I finally reached out to Dell Support about this issue. I was told that it is a known issue that version 2.3.0 newly installed on a PC running Windows 7 will prompt this error. The workaround for now is to uninstall DCU v2.3.0, install version 2.2.0 from the driver download page, then let it self update to 2.3.0. I can confirm that this works on the two models that I was having trouble with. The tech that I spoke with mentioned that they were in the process of publishing a KB article with this fix as well.
Run command update using some other admin account than build-in admin account, if domain enviroment add any accout to domain admins and try that or greate local account that is member of administrators.
That is how we fixed our issue, no need to disable virusprotection or anything else just running command update with other credentials.
MSeehase
1 Message
0
April 25th, 2017 11:00
Hello,
I experience the same issue with my XPS15 9560. Please let me know if there are any solutions for this problem. DCU version 2.3.0.
Kind regards
Martin
WxFisch
2 Posts
4
April 26th, 2017 08:00
I finally reached out to Dell Support about this issue. I was told that it is a known issue that version 2.3.0 newly installed on a PC running Windows 7 will prompt this error. The workaround for now is to uninstall DCU v2.3.0, install version 2.2.0 from the driver download page, then let it self update to 2.3.0. I can confirm that this works on the two models that I was having trouble with. The tech that I spoke with mentioned that they were in the process of publishing a KB article with this fix as well.
amjr
1 Message
0
October 24th, 2017 18:00
I would like to know if anyone would know how to create my catalog.xml in dell command update.
I need to update the drivers in a local on the network but I'm having trouble creating the xml file to call the driver could anyone help me?
BCOENeil
1 Message
0
March 19th, 2018 09:00
Thanks. Worked in 3/2018 too!
Ristus
1 Message
0
May 24th, 2018 03:00
Run command update using some other admin account than build-in admin account, if domain enviroment add any accout to domain admins and try that or greate local account that is member of administrators.
That is how we fixed our issue, no need to disable virusprotection or anything else just running command update with other credentials.
ckelley
7 Posts
0
June 15th, 2018 12:00
Were you running Command Update as Administrator?
I had a GUI-UVM15 error that went away when I ran it as Administrator.
twmmmason
1 Rookie
•
6 Posts
0
July 10th, 2018 09:00
Issue is happening again. Anybody else getting this error?
Drtrider
1 Message
0
July 26th, 2018 09:00
Can confirm WxFisch's fix has resolved the issue.
My situation;
Hope this helps someone else down the line! Thanks WxFisch!