Microsoft acknowledges a serious bug with Build KB4592438 that can affect computers with SSDs
Table of contents:
A few days ago we saw how the KB4592438 build was causing some problems for users who had ventured to install it. Problems with RAM consumption, PCU management and even blue screens to which is now added a serious problem with SSD hard drives
"A failure that has been echoed in BornCity and where they report that after executing the chkdsk c: / f command, a blue screen appears with the error message Stop-Error NTFS File System and from that point it is not possible to start the computer. A problem that Microsoft itself has already admitted"
SSD may be affected
Faced with the complaints of affected users and after verifying that the problem with the cumulative update KB4592438 and some SSD drives is palpable, at Microsoft they have only recognized the existence of the problem On the support page Microsoft describes the problem as follows:
In view of this problem, Microsoft support also details a series of steps to mitigate the failure and warns that restarting the device can help the resolution to be applied faster.
- The device should automatically boot to Recovery Console after failing to boot multiple times.
- Select Advanced Options .
- Select Command Prompt from the list of actions.
- Once the command prompt opens, type: chkdsk /f
- Allow chkdsk to complete the scan, this may take a while. Once complete, type: exit
- The device should now start as expected. If it reboots into Recovery Console , select Quit and continue with Windows 10.
After completing these steps, the device may automatically run chkdsk again on reboot. It should start as expected once it completes.
For company managed devices that installed this update and encountered this issue, it can be resolved by installing and configuring a Group Policy special.
For now there is no definitive solution and if you get that blue screen with said error, you will have no choice but to follow the steps recommended by Microsoft . It's clear that Microsoft updates are still not as reliable as they should be.
