KB4041691 Badly Botched

Status
Not open for further replies.
5

509322

Thread author
Some are reporting that when deleting all contents off of a USB flash drive that Explorer will crash.

Also, when ejecting a single USB flash drive while multiple USB flash drives are installed will also cause Explorer to crash and the remaining USB flash drives will disappear from Explorer.

Finally, copying files\folders can cause Explorer to crash. The size of the file\folder is a contributing factor.
 
Last edited by a moderator:
L

Local Host

Thread author
Some are reporting that when deleting all contents off of a USB flash drive that Explorer will crash.

Also, when ejecting a single USB flash drive while multiple USB flash drives are installed will also cause Explorer to crash and the remaining USB flash drives will disappear from Explorer.

Finally, copying files\folders can cause Explorer to crash. The size of the file\folder is a contributing factor.
Can't replicate those issues, I was messing with flash drives and copying of huge (50GB) files yesterday and the explorer worked normally, clearly another issue related to third-parties.
 
5

509322

Thread author
Can't replicate those issues, I was messing with flash drives and copying of huge (50GB) files yesterday and the explorer worked normally, clearly another issue related to third-parties.

Regardless of the cause, bug discovery is one of the reasons that Microsoft wants to force updates on everyone. And that's the purpose of these type threads - to inform the unwitting user as to what they might encounter with the post-apocalypse Microsoft update.

If something was working before a forced update and does not work after a forced update - whose fault is that ? It certainly ain't the 3rd-party's fault. And most definitely not the end-user's.
 
Last edited by a moderator:

brambedkar59

Level 29
Verified
Top Poster
Well-known
Apr 16, 2017
1,869
If something was working before a forced update and does not work after a forced update - whose fault is that ? It certainly ain't the 3rd-party's fault.
Sorry, I have to disagree. 3rd party software companies too share this fault as they didn't tested their software with the 'latest windows insider' update. And in the end it really sucks for the end user as usual.
 
5

509322

Thread author
Sorry, I have to disagree. 3rd party software companies too share this fault as they didn't tested their software with the 'latest windows insider' update. And in the end it really sucks for the end user as usual.

That's not how it works. Except for some general compatibility testing nobody does it. The Insider Builds are beta builds with rapid and large restructuring. Plus, Microsoft unilaterally makes changes without notice.

Everybody waits until the final, "stable" release. To do otherwise just ends up being a waste of time and effort in the end.
 
Last edited by a moderator:
Status
Not open for further replies.

About us

  • MalwareTips is a community-driven platform providing the latest information and resources on malware and cyber threats. Our team of experienced professionals and passionate volunteers work to keep the internet safe and secure. We provide accurate, up-to-date information and strive to build a strong and supportive community dedicated to cybersecurity.

User Menu

Follow us

Follow us on Facebook or Twitter to know first about the latest cybersecurity incidents and malware threats.

Top