New
#270
You get told again that no action is needed and they recommend you stay on the current version. The link for why am I seeing this is: https://support.microsoft.com/en-sg/...n-notification
Ak
You get told again that no action is needed and they recommend you stay on the current version. The link for why am I seeing this is: https://support.microsoft.com/en-sg/...n-notification
Ak
It had happened to me all the time after a FU. One thing to check is to see if "Remote Desktop" in Windows firewall is still ticked, taking into account that the new FU can change your settings. Open control Panel > Windows Defender Firewall > Allow an app or feature through WD firewall > Change Settings > Put a tick in front of "Remote Desktop" and reboot you machine:
Of course, you have to do the same for all the PCs on your network.
Last edited by IronZorg89; 23 May 2019 at 17:20.
Thanks for posting. Yours is a real issue, not just an external storage. I would wait.
Too bad the message you got doesn't just go one step further to state what driver or what hardware or whatever it found. Then you could come up with plan.
Of course some of the known quick fixes might apply.
from this doc.
https://docs.microsoft.com/en-gb/win...de/quick-fixes
Case proven. I have successfully recreated the problem and made 'Defer Features updates' disappear.
Setting the channel to 'Semi-Annual' (without 'Targeted') on its own had no effect. But setting 'Defer Features Update' to 7 days as well did. It removed the Defer Features update' setting. As yet, I've not been able to restore it. The defer quality updates is still there, but then I left that set at zero days. At this point for completeness I suppose I should try the same for the Quality updates setting, and try both with the 'Targeted' channel, but life is too short for that many 1903 upgrades
Edit: I have now reported this problem on the Feedback Hub. (anonymously, I'm afraid, as I don't have an MS account).
Last edited by Bree; 23 May 2019 at 11:19.
Yeah, but in my case when I got the error the ONLY USB card / thumb drive I had in my system was the USB thumb drive containing the update. What that means is even if you have NO USB drives installed prior to attempting to install the update, by virtual of using a USB thumb drive for install purposes will net that error.
My post here is a prime example of that. Bottom line is I wouldn't attempt to install from a USB device.
Yesterday, I didn't have usb or cards of any sort inserted from beginning on 3 systems and it still happened.
Whether by the assistant or via update, it still wouldn't work. Tried making iso via 1903 media creation and it still stopped, whether I chose the update option or for other pc.
Jumped onto insider vm and grabbed standalone 1903 iso and mounted this on all pc's....still no go.
Found an article online that said to do it offline, so I disabled network and it worked on all machines.
Now here's the bit that doesn't make sense.
Just did Dell laptop tonight and it worked without a hitch.
GREAT !!!