Dell Command Update 3.1.2 hangs with "Operation in progress".

Vostro 3670, Dell Update 3.1.3 - same error. Stuck @ 10% for hours.

Possible easy solution to hanging:

Installed v3.1.3 today on an aging Inspiron running Win7 & had same problem after installing Bios (operation in progress....)

A previous post mentions Dell Client Management Services (DCMS) which was started/running. Closed the  Dell Update program. Stopped DCMS with Task Mgr. Tried to reopen Dell Update but would not start; I thought that it would restart DCMS, but did not. Went back and restarted DCMS. Dell Update works fine; checked for updates - no hanging; ran update twice.

Note: With Task Manager in Win 7, you must click on Services button at bottom of Services tab to Start & Stop DCMS. Did not try Start/Stop in Win 10, but there is not Services button on its Services tab.

Hope this helps.

Hi, I worked for me. I've restarted the DCMS service during the Dell command update, twice, at the third time, Dell command update has arrived to 70% and then 100% showing all new drivers and bios.

Thanks

Thanks fot the suggestion, @Torpedillo .  When i stop the DCMS service, DCU closes immediately.  Does it continue running for you?

I had this issue on a Latitude 7200 2-in-1. My deskside techs confirmed they had seen it on all of our 7200s in the environment.

Seems if we rolled back and installed the 3.1.0 version the scan worked perfectly and finished within seconds like it should have.

Looks like the latest build version is buggy.

@blazius1  same issue here

Also, with 3.1.3 installed, DPO 6.4.5 "System updates" check results in a meaningless error.

Went back to DCU 3.1.0 as suggested above, and it works OK, even DPO works again now...

Hopefully DCU 3.1.4 will come soon and fix this

Had this problem on a Precision 3630 with DCU 3.1.3. Ran it over a weekend and came back to find it still stuck at 10%. Tried repairing, removing, and re-installing. Didn't help. Tried disabling the Dell service, renaming the folders in the ProgramData folder, didn't help. Uninstalled it, installed DCU 3.1.1 and that seems to have worked. So... bug in 3.1.3. 

I've tried literally everything, every version since the initial 3.1 to the latest 3.1.1 and all give the same result "Operation is 10% completed..." Uninstalled, Installed rebooted and rebooted again, rename folders, repair, services you name it I tried. I called Dell Support and explained each step that I had taken and was hoping that there was a registry entry to delete/apply to fix the error or something buried in the installation location that could be modified to allow the DCU to work again but the Dell Support Technician said that I had to reimage my laptop!! Seriously what kind of solution is that, the application has always be buggy..but reimaging is just too much and just ridiculous.C'mon dell 

A quick search of Dell Support yielded the answer. Here's what Dell support quotes as the problem.

"Dell Update and Alienware Update communicates with the Dell Client Management Service to perform the update tasks invoked by the user. When the user clicks "Check" on the Welcome screen, the application calls the service to perform a scan for updates. The service, in turn, will open C:\ProgramData\Dell\UpdateService\Clients\Update\Scheduler.dat to check for any scheduled tasks.

When Scheduler.dat is corrupted, the service gets an error and does not report back to the application which is expecting a response from the service. The application is left waiting and displays the last progress information that it received."

https://www.dell.com/support/article/en-us/sln322662/dell-update-or-alienware-update-stuck-at-operation-is-10-completed?lang=en

Follow the instructions and it corrects to problem.

Thanks for the suggestions and link, @kd6ftr - I have tried it, but it does not solve the problem on my system.

Any solutions? I got the same issue. 

Solution works for me. Even with DCU 3.1.3 and DPO 6.4.5.

Deleting Scheduler.dat didn't fix the issue for me. Any other suggestions? This is occurring on 5501.

Thanks, this worked for me.

Deleting Scheduler.dat didn't fix the issue for me. i have optiplex 7060