I ran the October update and lost my Desktop folder. After install, a dialog box appears: "C:\WINDOWS\system32\config\systemprofile\Desktop is unavailable ..."
Out of curiosity... why was your desktop folder there? That is a really weird place for it.
Even After Fix, Windows 10 Update Is Botching File Operations
51–60 of 159 posts
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#52I ran the October update and lost my Desktop folder. After install, a dialog box appears: "C:\WINDOWS\system32\config\systemprofile\Desktop is unavailable ..."
Out of curiosity... why was your desktop folder there? That is a really weird place for it.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#53An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.
[ https://win10.guru/how-i-lost-my-windows-insider-mvp-award/ ]
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#54If you're really tired of this shit, then get LTSB.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#55This article is super deceptive, these two bugs are completely unrelated, and the one still standing is pretty obscure: 1. You're extracting a Zip file and intend to overwrite your own data 2. The data isn't overwritten, but it doesn't tell you about it 3. You delete the Zip file, thinking that it's extracted. I'm not discounting that this is a Bug, but I can't think of a time I would've ever lost data because of thi…
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#56If you're really tired of this shit, then get LTSB.
I'm not sure how LTSB could have prevented this at all. Ironically, 1809 was a LTSB release, so if you were upgrading from 1607 LTSB (to get WSL working, for example), you would also be exposed to this bug.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#57If you're really tired of this shit, then get LTSB.
I'm not sure how LTSB could have prevented this at all. Ironically, 1809 was a LTSB release, so if you were upgrading from 1607 LTSB (to get WSL working, for example), you would also be exposed to this bug.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#58An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.
Seized, absolutely not. Of course since the government already has the source there is nothing that needs to be seized. The government can just declare the temporary monopoly that they granted on copying it to be over (to be clear, this would take an act of congress...). I'd almost be sympathetic to them doing that - but I also think the outcome would be absolutely terrible. Necessary maintenance (fixing security bug…
IANAL, but I think that would violate the Constitutional prohibition of Bills of Attainder.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#59An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#60Sounds like Linux-class bugs (e.g. KDE copy/paste not working correctly sometimes[0]). I guess Windows has lost its advantage of perceived quality. [0]: https://www.reddit.com/r/linux/comments/9a7k2i/psa_on_kde_ne...