[German]In Home windows 10 20H2 with installed cumulative substitute KB4592438, chkdsk causes huge points. It destroys the file system for the length of a disk take a look at on SSDs, so Home windows 10 can’t commence after a reboot. Here is about a files about the pronounce and the affected Home windows 10 produce.
I’ve been contacted by several German weblog readers by electronic mail and by feedback inside my German weblog (thanks for that). All of them pointing to a extra special trojan horse, obviously introduced to methods with cumulative substitute KB4592438.
The problem with ChkDsk
The problem became before the entire lot described by Nero24 within the German planet3dnow.de forum (the affected person contacted me by electronic mail). In a college, several methods with Home windows 10 20H2 already installed might additionally aloof be manually updates to the contemporary substitute situation (Home windows and Area of commercial updates). The administrator, who did the manual substitute set up, made up our minds to attain the next relate after finishing the artificial set up:
chkdsk c: /f
The intension is to check the Home windows force for wreck and (with the /f switch) at once wreck a repair. In the scenario described above, issues went very badly unpleasant. The affected person had seven methods, that can no longer boot after the file system take a look at collectively with repair. The guy became ready to prevent the re-boot from the a host of computers, after the seventh machine failed.
Conclude error NTFS File System, Source: planet3dnow.de-Dialogue board
The blue cowl shown within the screenshot above seems with the stay code NTFS File System (it presentations a NTFS FILE SYSTEM stay code, behold here for an English model of the BSOD). The affected person became ready to peek this on seven computers with Home windows 10 20H2. When examining the affected disks (SSDs) on a working system, it might perchance additionally very properly make sure that the logical Home windows force on the disk became detected utterly as a RAW partition. The /f probability of chkdsk likely destroyed the NTFS file system.
Extra prognosis of the RAW partition with chkdsk in offline mode printed errors with a corrupted ‘file 9’ and an error within the BITMAP attribute of the Master File Desk. These might additionally very properly be corrected with chkdsk in offline mode. After that, the methods booted another time after installing the SSD as a Home windows disk within the current PCs.
Error prognosis and condition
In the planet3dnow.de forum, the affected person offers some traits of the affected devices. Here is the relevant excerpt:
They are all Kaveri methods with ASUS A68HM-PLUS motherboard and Kingston SATA SSD running in AHCI mode with the Home windows favorite AHCI driver. First and necessary I suspected a harmful TRIM habits alongside with chkdsk and the indisputable truth that the system reboots at once after completion.
But they’re no longer identical SSDs. Most are Kingston A400s with Phison S11 controllers and 2D TLC NANDs, nonetheless there became also a Kingston V300 with Sandforce controller and MLC NANDs, which indubitably has a really a host of TRIM habits than the Phison-fired ones.
Whether the hardware has an impact is currently unclear. Interior my German weblog a user reported, that the error didn’t occur on two methods with laborious disks, nonetheless a Third system with a M2.SSD induced the BSOD as anticipated. The case became summarized on German plan planet3dnow.de in this article. There, the affected person writes that it impacts produce 19042.685 of Home windows 10 20H2. The cumulative substitute KB4592438 might additionally aloof be the perpetrator. The weblog reader wrote to me:
Indulge in you heard anything similar from your neighborhood in this regard? In the forum thread above, we had been ready to slim it down reasonably properly the set up apart it happens and the set up apart no longer, nonetheless I’d aloof be pondering external observations.
After publishing the German model of this weblog put up, several weblog readers confirmed this trojan horse. Must you might additionally occupy got extra insights, please fall a