1 Rookie

 • 

4 Posts

June 30th, 2022 01:00

https://youtu.be/RxUAuMMtgLw

A youtube video link showing the issue for your reference

Moderator

 • 

27.6K Posts

June 30th, 2022 00:00

Thank you! We have received the required details. We will work towards a resolution. In the meantime, you may also receive assistance or suggestions from the community members.

1 Rookie

 • 

4 Posts

June 30th, 2022 01:00

Thank you, much appreciated for the response

4 Operator

 • 

4K Posts

July 13th, 2022 22:00

I've found out it the Clients folder causing the Error: 1053 bug and had tried to change the security permission to full control for my user account then it works first time but fails on the second time, it seems to rewrite clients file. Dell need to fix this problem in the next update!

 

November 4th, 2022 16:00

Hi, I found this solution and it worked also for a problem with Dell's SupportAssist which failed to perform driver updates. Client Management Service didn't start until I could access the UpdateService folder and erase Clients folder. But then I got the same problem as AdrianG001.  Did you had the same issue? 

 

 

1 Rookie

 • 

4 Posts

November 4th, 2022 20:00

Hi, yes,

I have found similiar observation as Adrian there. Once you restart the system, folder permission resets automatically not allowing full access. I am suspecting that it could be possibly due to a corrupt microsoft profile to which i have not attempt to solve. I have left it as it is. I am keen to hear your findings in this.

 

Cheers

1 Rookie

 • 

30 Posts

November 8th, 2022 17:00

I am getting permissions issues - on my own machine?

1 Rookie

 • 

30 Posts

November 8th, 2022 17:00

Where is the UpdateService folder ?

2 Posts

September 2nd, 2023 00:38

It is now September 2023, Dell Update version 5.0 and issue is still happening to me. Every time when Alienware or any other software tries to update, I have to do this process or removing clients folder or it will fail.

1 Rookie

 • 

14 Posts

December 7th, 2023 15:45

@Paul1106​  much appreciated; that sure did the trick 

December 11th, 2023 19:10

So it's been over a year, and still no real solution to this? I bought an Alienware x17 R1 a couple years ago. The Alienware Update service has been working fine up until about a month ago. Now I have the same issue where trying to start the Alienware Client Management service is failing with the 1053 error code. I followed the instructions in the video that was posted above. It allowed me to run the Alienware Update service. However, it is not a permanent fix, and you have to repeat it each time you want to check for updates. Has anyone found a way to permanently fix this issue? I like to keep my system current with firmware and software updates, but it's become a real chore with this bug.

December 11th, 2023 21:19

I have a customer service ticket open with Dell. I've found a lot of other threads on Dell Community that mention this same issue, going all the way back to 2017 or earlier. Seems like someone would have figured something out by now to permanently resolve this issue.

5 Posts

January 12th, 2024 14:24

I have the same problem on a Dell Precision 7540 and a 7550. I had a ticket open with Dell Support and they finally told me to just update the computers manually because I cannot rebuild the computers because they are specialized computers for 3D modeling work. Neither Dell Command Update 5.1 nor the Dell Assist will function. 

1 Message

January 12th, 2024 16:58

I have the same issue on several Latitude 5520s, and a couple of 5520s.

I get error 1067 unexpected error when trying to start the Dell Client Management Service.

Been through the uninstall/reinstall of Support Assistant. Ran SFC /scannow until there were no violations.

Uninstalled/Reinstall Dell Command Update. Have an open T-Ticket with Dell, ran several t-shooting steps.

Check for Updates still not working.

Tried the steps in Paul1106's posted Youtube video above, now I get the 1053 error when trying to start the DCM Service.

Rebuilding is not an option due to remote workers in production.

Still trying to find a solution...

No Events found!

Top