3 ms·

In my case there is a glitch in the 1903 install where having external drives attached forces a fail as the installer can't determine which is the Windows drive

In my case there is a glitch in the 1903 install where having external drives attached forces a fail as the installer can't determine which is the Windows drive or something (per an error/forum I read at the time). I had coped the ISO from a USB so removing the USB drive resolved the error. I think it's picky to prevent issues similar to 1809 install. That was a mess and I'm sure MSFT would rather have an error before upgrading than a user missing all their data or something worse.

blattimwind 7y ago
> In my case there is a glitch in the 1903 install where having external drives attached forces a fail as the installer can't determine which is the Windows drive or something (per an error/forum I read at the time). All things old become new again. In the Vista and 7 era there were a bunch of updates that you just could not install if you booted Windows by chainloading its bootloader. You had to boot Windows straight from BIOS, otherwise they'd fail to install, because some obscure component in Windows couldn't figure out what C:\ was otherwise.
makomk 7y ago
The data loss issue in 1809 was the result of Microsoft intentionally writing and deploying code with the specific purpose of deleting people's documents directories and everything contained within them. The way to avoid this was not to program Windows updates to delete people's documents. (For anyone who doesn't know the context: Windows has the ability to redirect the various documents, music, etc directories away from their default locations. Some genius at Microsoft decided that any data left in the original location after such a move was junk and got a Windows 10 update to delete it. Unfortunately, Microsoft's own OneDrive software, which was bundled with and heavily promoted by Windows 10, intentionally redirected some of these folders without moving the contents in older versions and also often failed part-way through leaving some files behind in newer versions which promised to move the existing documents too. So a whole bunch of people who'd clicked Yes when Windows 10 pestered them to put their documents in OneDrive found that not only did it fail to do that, they got all their non-cloud-backed-up documents deleted a few Windows updates down the line. Making matters worse, some of the members of their crowdsourced beta-testing program had apparently hit this problem and warned them that the update was deleting people's documents, and Microsoft just ignored it and went ahead with the update anyway.)
- westmeal 7y ago
  Why am I not surprised

blattimwind 7y ago

> In my case there is a glitch in the 1903 install where having external drives attached forces a fail as the installer can't determine which is the Windows drive or something (per an error/forum I read at the time). All things old become new again. In the Vista and 7 era there were a bunch of updates that you just could not install if you booted Windows by chainloading its bootloader. You had to boot Windows straight from BIOS, otherwise they'd fail to install, because some obscure component in Windows couldn't figure out what C:\ was otherwise.

makomk 7y ago

The data loss issue in 1809 was the result of Microsoft intentionally writing and deploying code with the specific purpose of deleting people's documents directories and everything contained within them. The way to avoid this was not to program Windows updates to delete people's documents. (For anyone who doesn't know the context: Windows has the ability to redirect the various documents, music, etc directories away from their default locations. Some genius at Microsoft decided that any data left in the original location after such a move was junk and got a Windows 10 update to delete it. Unfortunately, Microsoft's own OneDrive software, which was bundled with and heavily promoted by Windows 10, intentionally redirected some of these folders without moving the contents in older versions and also often failed part-way through leaving some files behind in newer versions which promised to move the existing documents too. So a whole bunch of people who'd clicked Yes when Windows 10 pestered them to put their documents in OneDrive found that not only did it fail to do that, they got all their non-cloud-backed-up documents deleted a few Windows updates down the line. Making matters worse, some of the members of their crowdsourced beta-testing program had apparently hit this problem and warned them that the update was deleting people's documents, and Microsoft just ignored it and went ahead with the update anyway.)

westmeal 7y ago
Why am I not surprised