New
#200
I've had external drives that I had setup a Windows To Go install on, refuse to get a drive letter when plugged in. Even if I formatted them. I had to do a clean all on them to reset the no drive letter flag on them.
I've had external drives that I had setup a Windows To Go install on, refuse to get a drive letter when plugged in. Even if I formatted them. I had to do a clean all on them to reset the no drive letter flag on them.
I've seen a RAW drive that needed the clean to get it going again, as well.
I had one flash drive left plugged in that acted up while that became Raw not due to the upgrade install but the 3rd party app previously used for writing iso image files to bootable media now suddenly ended up being Raw flash drives after the program was showing the successful write of the iso. Different flash drives and differing downloads the 32bit and 64bit separate downloads as well as the MC Tool downloads all failed to write to flash drive even with the MC Tool at first. This is why mounting the iso became a mandate on all machines here.
Totally unacceptable risk at this point to me.
Losing data or lose access is definitely a no go option.
I wish they remove from thewebsite the ammiversary update at this point.
And who knows when they find a fix.
Of course i have the backup; i beleive that this is a very major bug.
So tjey had better find the fix, scrap 1607 and then publish a new version.
Too risky for me sorry
There is something about upgrading with the AU that is weird... I did the in-place upgrade from 1511 to 1607 and had corruption - SLUI.exe wouldn't run ( I do muck around with activation stuff to get some insight, so that may have been the cause) - anyway no activation - so resorted to clean install and copying files from mounted image.. reinstalling apps is not an issue as far I'm concerned (apart from from the time it takes, like a 7GB Visual Studio install) - and all's well.