![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
ty this and it works for me thnx you
That's the standard solution one when your update is stuffed prior to 23h2->24h2. The one you are regularly get given on Googles and solution but not good if it isn't your problem. You soon get tired of it.
The problem with updating drivers is that some drivers fail the initial part of the update at 20% or so, so you can introduce a problem that you never had. You should back up all drivers so you can roll back before updating drivers willy - nilly. For me updating drivers introduced an incompatible drivers that had been picked up in the development of 24h2 but never fixed. Reported on insider message boards. You should only in anycase where possible use the PCs driver site library. Some drivers are modified.
If it's a memory integrity issue of a driver the solution won't pick that up. My main issue, you need to run the Microsoft memory integrity test of the drivers and remove those that fail. Retry.
Hence a jaundiced view of these standard old timer fixes if it's an issue that is new to 24h2 which memory integrity test is. Plus try to update all drivers isn't the solution if there is a failure of the developers to release compatible drivers for the migration. That can introduce new problems that were not the issue. Either way you can circumvent that old timer fix by doing an inplace 23h2 update which is on the main menu of 23h2. Cuts out long lists of commands.