12-06-2020, 08:58 AM
31
Re: Microsoft Issues Windows 10 May 2020 Update Warning
There is no update being offered for the Intel NUC yet but I too now have the message...The Windows 10 May 2020 Update is on its way. We're offering this update to compatible devices, but your device isn't quite ready for it. Once your device is ready, you'll see the update available on this page. There's nothing you need to do at this time.
A strange one in a way because they must mean it the other way around. The update is not ready for my device, rather than my device is not ready for the update.
12-06-2020, 01:10 PM
32
Re: Microsoft Issues Windows 10 May 2020 Update Warning
Originally Posted by mart
->
There is no update being offered for the Intel NUC yet but I too now have the message...The Windows 10 May 2020 Update is on its way. We're offering this update to compatible devices, but your device isn't quite ready for it. Once your device is ready, you'll see the update available on this page. There's nothing you need to do at this time.
A strange one in a way because they must mean it the other way around. The update is not ready for my device, rather than my device is not ready for the update.
12-06-2020, 01:14 PM
33
Re: Microsoft Issues Windows 10 May 2020 Update Warning
One issue mitigated:https://docs.microsoft.com/en-us/win...004#421msgdesc
Last updated: June 09, 2020 10:01 AM PT
Errors or unexpected restarts for some devices using Always On, Always Connected
Some devices using the Always On, Always Connected feature might have compatibility issues with Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected devices will have more than one Always On, Always Connected capable network adapter, such as the Microsoft Surface Pro 7 and Microsoft Surface Laptop 3, and might receive errors or unexpected shutdown or restart.
To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.
Affected platforms:
Client: Windows 10, version 2004
Resolution: This issue was resolved in KB4557957. The safeguard hold is estimated to be removed in the coming weeks.
12-06-2020, 01:41 PM
34
Re: Microsoft Issues Windows 10 May 2020 Update Warning
I don't want it. Moving to Windows 10 from 7 was a hell of a mistake for me. It's totally screwed my computer, so much was lost that I used and it's now so slow with everything, if it does it at all. I'll not be letting anymore damn upgrades on this computer if I can possibly stop them. I liked Windows XP, it was reliable, quick, and seldom if ever a hitch.12-06-2020, 03:02 PM
35
Re: Microsoft Issues Windows 10 May 2020 Update Warning
Originally Posted by Omah
->
No, it's your fault for not having a new PC ..... now MS has to make the effort to compensate for your inadequacy (and mine) .....
I read elsewhere that there was some trouble regarding Intel graphics drivers and the 2004 update. Intel and Microsoft are/were working on it. 1909 is working well. I can just stay with that until the problems are sorted ..stay on it forever if necessary.
18-06-2020, 01:56 PM
36
Re: Microsoft Issues Windows 10 May 2020 Update Warning
Two issues resolved:https://docs.microsoft.com/en-us/win...004#421msgdesc
Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input.
See details > N/A
Resolved
June 12, 2020
05:06 PM PT
You might receive the error: Windows cannot find "c:\program files\microsoft office\root\office16\winword.exe"
See details > OS Build 19041.329
June 09, 2020
KB4557957 Resolved External
June 12, 2020
05:06 PM PT
18-06-2020, 04:30 PM
37
Re: Microsoft Issues Windows 10 May 2020 Update Warning
Originally Posted by Omah
->
Two issues resolved
My Intel NUC still wasn't being offered the update. Having read elsewhere that others were being blocked for no good reason they could see, I decided to bypass the message given on Windows Update and have another go (using the MS Update Assistant).
All done and everything is running well so far. I think bad luck was the reason for getting the strange graphics effect (post #20). It looks like it was caused by the mentioned monitor switching box and not the update.
Since the update on the NUC went OK, I went ahead updated an older (rather slow) computer that also was not being offered the 2004 update. This is running OK too.
Just got Mrs mart's Surface Pro to look at now.
|
|
