![]() Powershell $d = 'c:\win10exe' mkdir $d $ComObj = New-Object System. I don't want to have to lay hands on all of our PCs to update to the latest version especially with so many off site now. ![]() If anyone has been able to fix this I would be eternally grateful. I even checked the arguments and they look exactly the same. I checked the BlueBox logs and nothing seems super different except the old stations freak out about a commandline argument(which I can't alter in WSUS so what the heck). I was able to use the ISO to update to 20H2 on one computer but that is not sustainable. ![]() I just can't get these older workstations to take the update. I have blown out the SoftwareDistribution folder, deleted CBS, completely reset WUAUCLT on the workstation. However, since I have been rolling out some new workstations lately, I have found that the new workstations WILL take the 20H2 update without issue from WSUS. I am continually getting this error when trying to update existing 1909 workstations (many of which had been successfully updated from 1903 to 1909 via WSUS) to 2004 or 20H2.Įrror code 0XC190010a, MOSETUP_E_UNKNOWN_CMD_LINE ![]() I have been banging my head against a wall on this one for some time. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |