New
#50
Oh okay. Have you encountered any serious bugs so far in 1903?
Oh okay. Have you encountered any serious bugs so far in 1903?
Looks like this may be addressed by this Cumulative Update?
Cumulative Update KB4497935 Windows 10 v1903 build 18362.145 - May 29
So I guess I'll need to use "DISM /Add-Package" to add this update into the WIM from a 1903 ISO (?)Changelog for that update said:
(And I guess the SSU update which has also been issued today.)
From the article on the first page...
This makes no sense to me. Looking at my systems for example. I've NO external USB drives or card readers attached to any of my PC's to include laptops. Yet not one has been offered the update. According to the article, I'm not affect, and should have been offered the update. So what's really going on here?an external USB device, SD memory card or UFS card that is attached to the computer could cause inappropriate drive reassignment on Windows 10-based computers during the installation of the Windows 10, version 1903. For this reason, there is an update hold on computers from receiving the Windows 10, version 1903 when this is detected. This generates the error message that is mentioned in the "Symptoms" section if the upgrade is tried again on an affected computer.
Anyway, I did update a couple of my PC's via MCT. Of course the update complained I was using a USB thumb drive which I was... in order to install the update. Wound up copying the files from the thumb drive to a folder on the desktop and using the exe there. All good. Still, if you believe the article above, I certainly qualified seeing I've no USB external drives connected to my PC, yet no update offer
BTW I have five SSD drives total in my main rig to include two NVMe drives. Prior to the OS update, I disabled the three SATA drives in the BIOS. Both NVMe drives were left alone (one is the OS drive) as you can't BIOS disable those (unless I missed something). Anyway no drives were reassigned when I reenabled them - drive letters remained unchanged.
Here's a question though: Are mapped drives an issue? I disconnected them prior to updating, still...???
A laptop, though it shouldn't make a difference. What may make a difference is if you have multiple drives installed....
The good news is....Microsoft said:
https://docs.microsoft.com/en-us/win...903#467msgdescResolution: This issue was resolved in KB4497935. The safeguard hold will be removed following the June Update Tuesday release.
No, it's not a dumb question. The ISO currently made by the MCT is for the initial version 18362.30.
After this patch Tuesday, if the MS 'resolution' can be taken at face value, the v18362.30 ISO should be able to do an in-place upgrade with USBs attached, provide you let it check for updates as part of the upgrade. How/if that would work for a clean install, I can't say.