Even After Fix, Windows 10 Update Is Botching File Operations
1–10 of 159 posts
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#2Yikes. This sounds, however, like a completely different bug, if it is only triggered by unzipping archives. I'm sure that the situation is more complicated than it looks - because it looks like there is just a shocking lack of QA testing being done, if basic edge cases like this are resulting in undefined behavior.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#3while technically true, the title is misleading because it makes it sound like every file operation (copy, move, etc.) is botched, when in reality it's only messing up when extracting from zip files and they already exist.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#4I ran the October update and lost my Desktop folder.
After install, a dialog box appears:
"C:\WINDOWS\system32\config\systemprofile\Desktop is unavailable ..."
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#5Microsoft has turned Windows Update into a cancer that is the single reason I am going to abandon their platform in future machine purchases. Can't believe I'm longing for the days of Vista (well post-SP1).
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#6while technically true, the title is misleading because it makes it sound like every file operation (copy, move, etc.) is botched, when in reality it's only messing up when extracting from zip files and they already exist.
I see what you’re saying, but Microsoft is forcing the industry on a treadmill to upgrade as quickly as possible as they aggressively break stuff on their quest the twiddle Windows twice a year. They need to embrace quality control.
Handling zip files is a basic file system function in 2018. If they are fucking up basic operations like this, imagine how bad other parts of Windows are now.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#7This is ridiculous, but to save yourself, run backups. I've been doing a full system disk backup every 24 hours for the past 2 years. So far it has saved my bacon once.
Fwiw, i use Acronis for bups. The restore process for a 128gb ssd took about 10mins.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#8Yikes. This sounds, however, like a completely different bug, if it is only triggered by unzipping archives. I'm sure that the situation is more complicated than it looks - because it looks like there is just a shocking lack of QA testing being done, if basic edge cases like this are resulting in undefined behavior.
I'm astonished Microsoft doesn't have automated tests for something as mundane as testing their built-in zip archive extraction functionality.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#9while technically true, the title is misleading because it makes it sound like every file operation (copy, move, etc.) is botched, when in reality it's only messing up when extracting from zip files and they already exist.
I see what you’re saying, but Microsoft is forcing the industry on a treadmill to upgrade as quickly as possible as they aggressively break stuff on their quest the twiddle Windows twice a year. They need to embrace quality control. Handling zip files is a basic file system function in 2018. If they are fucking up basic operations like this, imagine how bad other parts of Windows are now.
I agree with a lot of this, but I think if we are talking updates as upgrades, the industry and consumers forced their hands with fast update cycles with meaningful feature adds. Not excusing what is happening here, they allowed it to be released, but I do think they were forced into the current position rather than took it on their own.
Re: Even After Fix, Windows 10 Update Is Botching File Operations
#10It's not clear from the article whether this was just an old long-standing bug that has now gotten attention, or if they really broke a basic piece of functionality that has been around since at least XP if not earlier. I'm not surprised either way, but unfortunately I'm leaning toward the latter.
I don't think I'm the only one when I say I want Microsoft to quit messing around with Windows --- just fix the severe security bugs as they're found, and stop rewriting things needlessly. Then again, they're probably doing the latter as an excuse to insert telemetry and ads...