KB4041691 Badly Botched

  • Thread starter Thread starter 509322
  • Start date Start date
Status
Not open for further replies.
Lockdown said:
BSODs
DRIVER_CORRUPTED_EXPOOL

Some driver.
Click to expand...
I delay mine in both categories by 2 weeks, I hope that will be enough, I learned to do this from MS and many update re-installs due
to corrupted OS elements due to wonky updates :eek:
Thanks for the heads up Jeff.
 
  • Like
Reactions: brambedkar59, Cats-4_Owners-2, Venustus and 2 others
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:
  • Like
Reactions: mlnevese, Cats-4_Owners-2 and XhenEd
Lockdown said:
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.
Click to expand...
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.
 
  • Like
Reactions: Weebarra, mlnevese, Marko :) and 2 others
Local Host said:
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.
Click to expand...

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:
  • Like
Reactions: Venustus, Deleted member 65228, Marko :) and 3 others
Lockdown said:
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.
Click to expand...
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.
 
  • Like
Reactions: Venustus, Local Host, Marko :) and 1 other person
rockstarrocks said:
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.
Click to expand...

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:
  • Like
Reactions: Deleted member 65228, Marko :) and brambedkar59
Status
Not open for further replies.

You may also like...