The strangest Windows 8.1 problem I've ever faced... what even is this?

F5F Stay Refreshed Software Operating Systems The strangest Windows 8.1 problem I've ever faced... what even is this?

The strangest Windows 8.1 problem I've ever faced... what even is this?

The strangest Windows 8.1 problem I've ever faced... what even is this?

Pages (2): Previous 1 2

W

wdupuy71
Member

170

11-03-2016, 10:32 AM

#11

No problema, 113 GB disponibles en lugar de 223 GB.

W

wdupuy71

11-03-2016, 10:32 AM #11

No problema, 113 GB disponibles en lugar de 223 GB.

H

HDellrON
Senior Member

257

11-09-2016, 05:46 AM

#12

Performed a bootup scan with Avast...no malware found but a few files were damaged.

H

HDellrON

11-09-2016, 05:46 AM #12

Performed a bootup scan with Avast...no malware found but a few files were damaged.

E

eduardodd08
Posting Freak

852

11-09-2016, 09:51 AM

#13

If SFC and DISM fail to repair, it may indicate bad sectors on your hard drive. You can fix this using CHKDSK within a CMD window, but first consider running HDD Diagnostics. Recommended tools are Seagate Seatools or WD Data Lifeguard. If diagnostics confirm the drives are healthy, proceed with CHKDSK options. However, if diagnostics report a bad drive, using CHKDSK risks data loss. Please try the recommended software and share your findings.

E

eduardodd08

11-09-2016, 09:51 AM #13

If SFC and DISM fail to repair, it may indicate bad sectors on your hard drive. You can fix this using CHKDSK within a CMD window, but first consider running HDD Diagnostics. Recommended tools are Seagate Seatools or WD Data Lifeguard. If diagnostics confirm the drives are healthy, proceed with CHKDSK options. However, if diagnostics report a bad drive, using CHKDSK risks data loss. Please try the recommended software and share your findings.

L

Logarion
Member

202

11-09-2016, 03:41 PM

#14

I actually own an SSD. After following a recommendation from @RH00D about using Avast and performing a boot-up scan, it detected no threats but identified some corrupted files. I managed to fix them temporarily. Then I ran sfc /scannow, which found corrupted files and reported it couldn't fix some of them. Following up with dism /online /cleanup-image /restorehealth completed the process, and the component store corruption was resolved. Thank you for your assistance—I really value it.

L

Logarion

11-09-2016, 03:41 PM #14

I actually own an SSD. After following a recommendation from @RH00D about using Avast and performing a boot-up scan, it detected no threats but identified some corrupted files. I managed to fix them temporarily. Then I ran sfc /scannow, which found corrupted files and reported it couldn't fix some of them. Following up with dism /online /cleanup-image /restorehealth completed the process, and the component store corruption was resolved. Thank you for your assistance—I really value it.

O

oOEmmaOo
Posting Freak

818

11-10-2016, 12:27 AM

#15

Great! Everything came together smoothly.

O

oOEmmaOo

11-10-2016, 12:27 AM #15

Great! Everything came together smoothly.

Pages (2): Previous 1 2