|
Post by Jos on Oct 27, 2021 18:14:15 GMT 1
I would guess vDos doesn’t need to run elevated, so ADMIN=ON has no effect…
Jos
|
|
|
Post by Jos on Oct 31, 2021 19:41:03 GMT 1
I got the following findings by email: Basically I could not fix it, I just rolled back and postponed updates on 5 of 6 clients. The update that caused my problem was KB5005565. Also see references to KB5006670. It appears Microsoft is finally working on it : docs.microsoft.com/en-us/windows/release-health/status-windows-10-21h1#2737msgdesc (look at known issues) ================== During the process, I found that it is possible to delay windows update more than 7 days by doing this: - Pause updates for 7 days
- Resume Updates
- Immediately Pause Updates again
- Now you can re-click pause updates 5 more time, or about 5 weeks
================== The sixth client was fully updated so I used it for a test machine. I was just now able to get it working from information I found here: www.bleepingcomputer.com/forums/t/759880/kb5006670-network-printer-problems-again-this-month/What I did was replace the three system32 print spooler files mentioned late in that thread (page 12 #170) with versions from one of the rolled back workstations: I had also added this registry entry to both the print server and WS#6. I don’t know if that made any difference. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print] "RpcAuthnLevelPrivacyEnabled"=dword:00000000 In all cases, the first time I tried to print, there was a long timeout…then it printed. Could be some firewall or AV process looking at it. Also, in my case, it appears the print server computer does have the latest updates installed. It was the clients that I needed to roll back.
|
|
|
Post by steve on Nov 1, 2021 11:21:06 GMT 1
Thank you for the detailed information. I guess the best course of action for us to take (if we can) is to wait for MS to fix the problem (whilst not introducing other new, varied and exciting problems)!
|
|
|
Post by Jos on Nov 1, 2021 13:02:48 GMT 1
If all fails, an option could be a separate print server device with a RJ45 and USB and/or parallel connections…
Jos
|
|
|
Post by steve on Nov 12, 2021 13:09:51 GMT 1
Has anyone tried STOPUPDATES10 to pause the updates until a M$ fix arrives?
Steve
|
|
|
Post by steve on Dec 20, 2021 12:16:13 GMT 1
|
|
|
Post by gokulakkannan on Dec 28, 2021 4:21:51 GMT 1
Friends don't install vdos in to other hard drives(Except C drive). It is all creating problems. vdos programmers assumed or basically constructed to work with c drive only. so if you install it into c drive all your problems will be solved.
|
|
|
Post by emendelson on Dec 28, 2021 4:24:44 GMT 1
Friends don't install vdos in to other hard drives(Except C drive). It is all creating problems. vdos programmers assumed or basically constructed to work with c drive only. so if you install it into c drive all your problems will be solved. That's very strange. I've been using vDos on drive E: for five years with no problems at all.
|
|
|
Post by Jos on Dec 28, 2021 7:51:00 GMT 1
Friends don't install vdos in to other hard drives(Except C drive). It is all creating problems. vdos programmers assumed or basically constructed to work with c drive only. so if you install it into c drive all your problems will be solved. That is nonsense, vDos is fully portable and so vDos.exe can be located anywhere. For instance even on a network share without a Windows drive letter assigned to it. Maybe you are confused by DOS/vDos C: mostly not being Windows C:? Jos
|
|