Microsoft has confirmed that Windows 11 customers are additionally experiencing an odd bug with SATA arduous drives that has already been witnessed plaguing Home windows 10 (and certainly Home windows 8.1 and seven).
Neowin studies that Microsoft tell us this downside impacts Home windows 11 by way of a help doc that discusses the glitch, and advises customers what could be performed about it.
The bug causes an inside SATA drive – this may have an effect on each arduous drives and SSDs which can be put in inside your PC by way of a SATA connection – to be detected as detachable media within the Home windows taskbar, versus a completely connected drive (which, after all, it very a lot is).
Microsoft explains: “Whether or not or not a tool is taken into account detachable is set by your system’s BIOS and the way it marks the assorted SATA ports on the motherboard.
“The inbox driver immediately inspects SATA ports and considers units related to these ports marked ‘exterior’ as detachable units. Not all storage drivers do that, which could be a potential trigger for corruption or information loss.”
Evaluation: A repair is on the market, luckily
The excellent news right here is that many fashionable programs received’t be affected by the bug, as most SSDs today aren’t SATA – and arduous drives are a bit of tech that’s on the best way out, and very much doing a vanishing act.
Nonetheless, that’s to not say that there aren’t loads of PCs on the market with a SATA drive in them, even when solely an outdated arduous drive recruited into the combo for media storage duties, say.
The excellent news is that Microsoft supplies the main points of a repair within the help doc. As Microsoft advises, the very first thing to do is to test for a BIOS replace on your motherboard. If you happen to haven’t acquired the newest model, replace it, and preserve your fingers crossed that this may occasionally remedy the problem.
If it doesn’t, otherwise you’re already on the most recent BIOS – don’t flirt with putting in any beta BIOS, by the best way, it’s simply not definitely worth the danger – then Microsoft outlines directions for manually coping with the issue here.
Notice that you’ll have to enter a prolonged command (which just about seems like gobbledegook) so be sure to get this proper. It’s a contact fiddly, and includes tinkering with the Registry, so a mistyped mistake could possibly be unhealthy information – simply be very cautious you sort in precisely what Microsoft says within the closing step (for Home windows 8 or later, which clearly contains Home windows 11 customers).
Discussion about this post