My apps are suddenly "corrupted or unreadable" once more?
My apps are suddenly "corrupted or unreadable" once more?
Today several applications on the taskbar kept showing the same error message. The issue occurred whether I opened them directly from the start menu or by launching them from the Program Files folder. The setup files for these apps also reported the same problem. This is the third occurrence of this problem. Initially, I resolved it by reinstalling the applications, thinking it was a temporary glitch, but now it seems to be a recurring issue with no clear cause. After restarting Windows Explorer, all the app icons disappeared when they stopped working properly. It appears that around 70% of my apps are affected, though some remain unaffected. I ran an integrity check using sfc /scannow and found no violations. A chkdsk scan also completed without issues. A malware scan came back clean, and a reboot didn’t help. I’m currently using Windows 11 with update KB5044033. My CPU is an AMD Ryzen 7 5700G with Radeon Graphics at 3.80 GHz, and I have 32 GB of RAM. Anyone has any suggestions on what might be causing this?
An intriguing issue because it appears in multiple locations.
There might be several explanations for this.
If the concern isn’t ransomware, I’d start by searching for crystaldisinfo.exe downloads and examine the data on your storage device.
For an older mechanical HDD, the drive head could be missing alignment markers due to normal wear in its bearings. This issue begins small but worsens gradually. The tool should provide a health assessment of the drive.
If the drive’s health remains satisfactory, I can guide you further.
Should the health be poor, there’s still a chance to address it.
In the simplest scenario where your HDD is failing and just beginning to show signs, turn off Windows sleep features and let the system run overnight without sleeping. This allows the system to enter idle mode, after which it will attempt a background repair of the drive. It will read each sector, and if a CRC error occurs in a cluster, Windows will repeatedly try to recover until it obtains a clean copy. Once successful, it writes the data elsewhere and marks the original spot as faulty. This process may take several hours, especially if your system sleeps quickly.
Regardless, assessing drive health is essential to gauge how much time remains on the device.
Other potential reasons exist, but you should share details about your boot drive first.
Note: You ran sfc.exe /scannow and chkdsk, yet it’s wise to also run cmd.exe with admin privileges and execute DISM.exe /Online /Cleanup-Image /RestoreHealth. This would verify or repair any altered Windows core files by comparing them against a trusted source (Microsoft server).
Additionally, consider removing the pagefile.sys reboot and creating a new one to help eliminate any malware affecting virtual memory.
Es ist mir sicher, es handelt sich nicht um Malware oder Ransomware. Ich habe verschiedene Antivirenprogramme ausgeführt.
Es handelt sich um eine relativ neue 1 TB SSD.
Das Gerät wurde erst im Mai dieses Jahres gekauft.
Laut CrystalDiskInfo zeigt alles einen Wert von 100 % an:
the following steps would come next: i would try to refresh the firmware for each storage unit. beginning with the C drive: then adjust the BIOS, addressing any BIOS-related issues, followed by updating the CPU chipset driver on the motherboard. after that, check for any additional motherboard drivers related to storage. i assume you aren’t employing RAID technology. what is the boot device for your Windows system? if the C drive is the KINGSTON SNV2S1000G, could there be a risk of overheating in the electronics? in such cases, try powering off the machine, waiting about 20 minutes for it to cool, then restart and observe if the issue persists. using a cooler or heat gun on the component might help determine whether it’s preventing or contributing to the problem. note: some vendors offering inexpensive drives with mixed components often face unusual problems, such as timing errors or firmware glitches. excessive heat can lead to connections expanding and becoming misaligned. since the Windows image might already be present in RAM from the pagefile.sys, the system may seem operational until you actually need to read data from the disk—then an error occurs. previously, I encountered this issue with certain SATA drives; they would disconnect and required enabling hotswap on the SATA port before reconnection. otherwise, the system could take hours to check for errors after disconnection, depending on RAM size and file access patterns. nvme drives cannot be hot-swapped. if the device becomes warm and disconnects, it won’t automatically reconnect until the computer is restarted. I’m uncertain how Windows’ plug and play feature would handle this. i would probably open the Windows Control Panel, use Device Manager, go to the View menu, and check for hidden devices—then inspect the device tree to see if the drive appears grayed out (indicating removal). removing a device via hotswap could potentially corrupt the filesystem, which might be resolved by running chkdsk during the next boot.
if you aim to increase failure rates for testing:
you could also try downloading microsoft RAMmap from here
https://learn.microsoft.com/en-us/sysint...ads/rammap
extract the rammap64.exe file and execute it with admin privileges.
look for the empty menu option and select all available items.
run it, wait about five minutes, and observe if the drive heating becomes the reason for failure when launching an application. (if not, the app might already be in standby mode and wouldn’t fail because it doesn’t need to load from storage)
note: i’ve noticed nvme drives failing, and the solution was to slightly reposition the drive in the slot before securing it. that means loosening the screw and gently flicking the card to adjust alignment, then tightening the screw.
Johnbl here, just checking in on the situation.
It seems there are no new firmware updates for either drive.
The tests look fine, though the SSD is consistently at 31 degrees.
I’ve refreshed all motherboard drivers and updated the BIOS.
Also, I reinstalled ExplorerPatcher, thinking it might be related to taskbar issues—though probably not.
Using Open-Shell Menu helped remove those annoying windows tiles, and it hasn’t had any problems before.
Still puzzled about why setup files remain corrupted even when the drive disconnects. They seem to stay messy after a reboot too.
File explorer occasionally freezes, requiring a Task Manager restart.
After running sfc /scannow, Windows Resource Protection didn’t detect any integrity issues.
Then I tried DISM commands—no corruption found in the component store.
Cleanup and health checks completed without problems.
Unclear if these steps actually made a difference.
I do remember my restore points from when I first set up the machine, plus the ones I created after the first app failure about 3–4 weeks ago. Now I only have today’s restore points from the Windows update and chipset drivers.
It might be that the System Volume Information was deleted and recreated?
That sounds a bit strange.
Considering it might happen again, I plan to replace the current C drive SSD with a Samsung 990 Pro 1 TB SSD as their prices have dropped significantly.
if you are unable to update the firmware on an electronic drive, the next action is to boot into BIOS and leave the machine for a few hours. This may resolve situations where the drive falls behind its firmware garbage collection. If Windows is running, the firmware cleanup begins five minutes after Windows becomes idle. Occasionally, sleep functions may shut down the drive before the firmware finishes its cleanup tasks.
This issue becomes more noticeable when formatting a drive and reinstalling Windows. After deleting all files, the drive might appear empty, but the firmware still needs to perform cleanup on each module of the disk memory. The problem is more pronounced with low-cost memory due to its compact design. If the firmware struggles, it may not respond within the timeout period, leading to the error you encounter. Those who repeatedly face this error often reinstall Windows, which can worsen the situation. Others who overlook the warning assume the issue resolves after a few days.
You might also try telling Windows not to sleep the drive too quickly—perhaps set it to sleep after 30 minutes of inactivity, allowing the drive 25 minutes to complete its cleanup.
I just observed that many .jpg files were also 'corrupted,' but they functioned when imported into a program. However, after reassociating them with Picassa (my photo viewer), they became uncorrupted.
Looking at my Program files and Program Files (x86) folders, some programs are corrupted while others are not. It's strange.