@izzion said in Windows 10 reinstall:
This is normal, long term Windows installer behavior, and frankly the most correct behavior. Unless you tell Windows during setup to configure a partition on a drive, it will not try to create a partition on the drive or otherwise mount the drive during setup, waiting until you can use Disk Management during the full OS to tell it how to handle the drive (assign it a letter, reformat it, etc etc).
I deleted old partition, created new one and formatted it.
After installation the drive was not visible and there was no indication that it's connected at all. If this is correct behavior, it surely is not intuitive.
Local accounts (even via a Microsoft account) have Security Identifiers (SIDs) that are based on the install GUID of the system. Installing a new system and recreating the same account names will result in different SIDs, since they were created in different systems. Most other major applications (Microsoft SQL server) also behave this way - and that should be the most expected behavior, in my opinion, so someone can't just set up a different SQL server and suddenly impersonate all your users with the password of the new server (thus bypassing having to know the password on the old server). Obviously, for a local installation, physical access is root access and you can easily bypass the security to regain control of your files.
Why do I have to 'regain' access if I'm the user that created those files, plus I'm the system administrator that can take ownership with two clicks? Why the 'access denied' stupidity, it makes no sense.
Hrm, that error is "access is denied"... I wonder if something funky happened with the permissions of your AppData folders when you moved them around. Can you install any other Windows Store app that you install by "choice" (as opposed to the ones WU "helps" you with)?
No, it happened before I moved AppData folders.
Applies to Windows 8, but might be relevant for Windows 10 (might not be, YMMV...)
There's a new version of this troubleshooter, for W10. It didn't help.
Bonus problem: Directory Opus doesn't open when I click its icon on the task bar. It worked an hour ago and it still opens when I click the tray icon. My bet is on 'updates were installed'.