New
#40
Brink, Thanks for updated my post with the additional links. I missed your earlier post.
Jim
Brink, Thanks for updated my post with the additional links. I missed your earlier post.
Jim
Note The drive reassignment is not limited to removable drives. Internal hard drives can also be affected.
That's an interesting question...
My system has 2 x SSD and 4 x HDD, two of the HDDs are in a hot-pluggable bay; all drives are connected to the MB's SSD ports. The two SSDs have W10 1809 installed, updating W10 on both drives did not cause any issues previously. Maybe because the user folders had not been moved?
In addition, there are three network drive mapping as well.
For the time being, I'll just leave a USB drive connected, which is connected most of the times anyway...
Microsoft blocks Windows 10 May 2019 Update with USB device or SD card
This could be very important that they do this, as the Insider Edge and Google Chrome allow accessing USB devices on the web, and it could be a catastrophe if an upgrade happened just then.
chrome://flags/#new-usb-backend
USB Devices - Google Chrome
https://developers.google.com/web/up...ces-on-the-web
As the First Post has been updated to say that this affects "Windows 10 Insider Preview Build 18877 and later builds." and there are comments following about another build being imminent, one hopes that by May when the "final" release occurs, MS will have resolved this issue.
I mean, they'd never release a major build with such a problem....would they?
Oh...sorry...forgot the 1809 cock-up (Removes tongue from cheek)
Once again Thanks to all you Insiders for taking the heat
I have since disconnected DVD & Blu-ray drives, 2 x HDs, internal card reader/USB hub, disconnected 2 x network drives and ensured no usb/card devices are inserted but I still get the same error
The only thing still connected is my OS SSD
What else can I try?
Why am I still getting this error?
This is for going from 18875.1 to 18890
Other than a clean install is there any work around for this issue?
Issue now resolved. I had Battleye installed
Likely leftover when my son temp. installed Steam for test purposes
This MS script was useful, https://aka.ms/AppRPS
Even after deleting Battleye folder I still needed to delete the service (disabling was't enough)
start a command prompt as administrator and enter “sc delete BEService”
The upgrade then proceeded as normal for me
Does anyone know if this error occurs when trying to do a clean install of 1903 with a USB drive?