Microsoft resets 'days since last Windows 11 problem' counter to 0
- Reference: 1744194794
- News link: https://www.theregister.co.uk/2025/04/09/microsoft_resets_the_days_since/
- Source link:
The hold is due to a compatibility issue between the driver and Microsoft's flagship operating system. It was added on April 4, the same day Microsoft was celebrating the 50th anniversary of the company's founding.
The driver provides encryption protection and is used by security software, usually in the enterprise. The compatibility issue can cause affected devices to stop responding and display a black or blue screen error. [1]According to Microsoft , "This driver can be automatically introduced into a system as part of the installation process of many different applications.
[2]
"The issue impacts devices with any version of the sprotect.sys driver (1.0.2.372 and 1.0.3.48903)."
[3]
[4]
The issue is the latest in a long line for Windows 11 24H2, which, it is fair to say, has not been a stellar success for Microsoft. The list of problems exceeds those in the previous version, according to the company's release health dashboard. This might indicate that the company is becoming more open about problems in Windows or that testing quality before release has continued to decline. Or perhaps it is a combination of the two.
As far as this latest snarlup is concerned, Microsoft said, "SenseShield is currently investigating this issue. Microsoft is collaborating with SenseShield, and we will provide more information when it is available."
[5]
No estimate is available for when it will be fixed, just a warning not to force Windows 11 24H2 onto a system via a manual update or the installation assistant until the problem has been sorted out.
Microsoft has applied several compatibility holds since Windows 11 24H2 was released. Errors were [6]reported with devices that used the Dirac Audio enhancement technology, treating users to the blissful sound of silence. Earlier this year, the operating system [7]tripped up over a glitch with AutoCAD 2022 .
[8]Microsoft lists seven habits of highly effective Windows 11 users
[9]Bad luck, Windows 10 users. No fix yet for ransomware-exploited bug
[10]Introducing Windows on arm. And by arm, we mean wrist
[11]Windows 11 poised to beat 10, mostly because it has to
The Dirac problem remains outstanding until " [12]the driver addressing this issue is released by the manufacturer ." AutoCAD provided an update to deal with its Windows 11 24H2 issue.
The growing list of concerns, particularly connected with services that worked on previous versions but are misbehaving on Windows 11 24H2, is a worry considering the importance that Microsoft places on backward compatibility.
It might also be a factor in users looking askance at Microsoft's flagship operating system compared to their existing and functional Windows 10 installations. ®
Get our [13]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2#3509msgdesc
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Z_aZni3w13fGpm55lPgIcwAAAZM&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z_aZni3w13fGpm55lPgIcwAAAZM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z_aZni3w13fGpm55lPgIcwAAAZM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z_aZni3w13fGpm55lPgIcwAAAZM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://www.theregister.com/2024/12/19/windows_11_24h2_issues/
[7] https://www.theregister.com/2025/02/26/windows_11_24h2_autocad/
[8] https://www.theregister.com/2025/04/09/microsoft_windows_11_tips/
[9] https://www.theregister.com/2025/04/08/patch_tuesday_microsoft/
[10] https://www.theregister.com/2025/04/05/windows_smartwatch_hack/
[11] https://www.theregister.com/2025/04/04/windows_11_market_share/
[12] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2#3488msgdesc
[13] https://whitepapers.theregister.com/
M$
Can't code.
Won't test.
Give them all of your money (+10%)!
Re: M$
So somehow it's Microsoft's fault that a third party wrote a bad driver ...
You can argue you shouldn't get a stop error but you're ignoring thirty years of history, including third parties whinging that they were being locked out if Microsoft didn't allow them to write and install those crap drivers.
Re: M$
Yeah, the M$ "ecosystem" has been broken like this for 30 years, I am not ignoring it.
Only M$ has the "secret sauce", and will blame everyone else when things go wrong.
I agree it must be hell to write drivers for M$, but that is still the situation today.
Closed source sucks.
Re: M$
Uhhh, the "bad driver" is apparently just fine, thank you, for Win 10 and prior versions of Win 11. So I'd think that there was nothing wrong with the driver, but rather something wrong with the thing that the driver interacts with.
Re: M$
Dave, m'man, it ain't a 'bad driver' if it worked on all previous OS versions it was supposed to, going back to Win10. It's not the bloody driver that's the problem, it's bloody Microsoft FUCKING AROUND with the internals of the OS and NOT TELLING ANYONE until something breaks and NOT TESTING A DAMN THING until something breaks. Microsoft has done this with earlier versions of Win11. And Win10. And Win8.x. And Win7. And WinXP. Indeed, MS has done this at least as far back as DOS. Microsoft have been silently fucking things up for OVER 40 BLOODY YEARS. And it's gotten WORSE over time.
There is simply no excuse for this kind of thing, not this late in the game. Microsoft needs to fix their processes. Microsoft needs actually to TEST THINGS; minor, unimportant stuff like, oh, networking (wired and wireless), printing, and, oh, ENTERPRISE-LEVEL SECURITY. It's one thing if a one-man band putting out an obscure Linux or BSD variant fucks stuff up. It's an entirely different thing when the LARGEST SOFTWARE COMPANY IN THE FUCKING WORLD fucks things up. Repeatedly. See, for example, lots of El Reg stories such as https://www.theregister.com/2025/03/26/microsoft_deborks_usb_printers/ and https://www.theregister.com/2025/01/02/scanner_canon_windows_update/ and https://www.theregister.com/2024/12/11/microsoft_windows_11_escl_fix/, and that's just the last few months. There're a lot more where those came from. There's a reason why many admins let someone else be the first to apply Patch Tuesday patches; no one, including MS, has the least idea what will break this time. Because MS DOESN'T BLOODY TEST A FUCKING THING.
Yeah. I got shouty. And profane. Not sorry. Microsoft should be.
Such inefficiency, such waste
Better get Musk and his magnificent DOGE Team onto it.
Once he’s sorted out all of the Government systems, say next Thursday?
Re: Such inefficiency, such waste
BTW everyone don't forget to continue to fund Musk by using Twatter.
Backward compatability is why there are security holes.
They tighten the security of the OS and things break, hmm, go figure. This happens in Mac OS too when a new version is released. In the Mac's most recent version many print drivers just display a long list of options instead of the useful menu for instance.
KB5055523 borked my computer last night - this is the 3rd different security update and 24H2 itself, that has caused issues.
Sick and tired of having to resolve these issues, wasting many hours of my precious time.
Its got to the stage where I can no longer trust any cumulative update from MS.
Forunately I had a backup from the last resolution, and was able to get my system up and running again.
KB505553 just crashed on installation, wrecking thw windows update component store.
Even DISM, and SFC couldnt sort it out and failed.
All updates have been put on hold for 5 weeks.
Why did they splurge on a counter?
They could have used a jpeg.
It's not that bad! My own 'hours since last Microsoft problem' counter occasionally exceeds zero. When I'm asleep. Or on holiday.
Maybe someone should file a bug report...
Because that stupid counter just keeps resetting itself to 0...