Jump to content

Change Mode

Search the Community

Showing results for tags 'chkdsk'.

The search index is currently processing. Current results may not be complete.
  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • PC Matic Site
    • Information Desk
    • OverDrive Test or AutoFix Problems
    • PC Matic's Paid Products
    • Site Feedback
    • Tech Talk
  • Community
    • Networking, Email, and Internet Connections
    • Viruses, Spyware, Adware
    • User to User Help
    • Tips 'n' Tricks
    • Post Your Pit Test Results
    • Linux
    • Custom PCs, case mods, overclocking
    • Smart Phones and Hand-held Devices
    • Games and Gear
    • Distributed Computing Teams
    • General Discussions


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







System Specifications:

Found 2 results

  1. I tried UPGRADE win 7 pro to win 10 pro story here >>> // but failed due to errors in SSD disk or due reserved partition has assigned letter but must't have letter... what you think? https://www.tenforums.com/general-support/150782-repair-even-not-yet-set-up-yet-first-time-dvd.html#post1844837 according to attachment below - C:/ was the system drive... why the >>> why this shown F:/ 220GB rather c:/ ... in diskpart? what to do? chkdsk /f F: or...? I THINK RESERVED PARTITIONS DO NOT HAVE LETTER, I AM CORRECT? remove letter in reserved partition in diskpart assign letter of F: as c:/ in diskpart and try repair / upgrade continued?????? https://www.diskpart.com/diskpart/assign-drive-letter-4125.html CAN TRY THIS??
  2. I have a desktop PC running Windows 7, and no other OS, and it was working fine. And since I was going to go down to a friend's house to fix his non-booting Windows 10 PC, I copied Windows 10 from disc to a USB stick (via Rufus, a bootable USB stick creator program), and to test the Windows 10 USB stick was working, I booted up my Windows 7 desktop via the USB stick, got to the Windows 10 menu, and turned off the Windows 7 desktop. I did this because I thought that the Windows 10 installation USB wouldn't actually change anything on the PC until I told it to (which I wasn't going to do, of course, I just wanted to test that the USB stick booted). Anyway, the Windows 7 PC still works fine, i.e. online works, no viruses or malware, every program I've tried works, but whenever I boot it up, the Windows 7 PC ALWAYS runs CHKDSK at boot, then it tells me that CHKDSK can't check the C: drive, and tells me it's because of some previously installed software, and that I should use the system restore to go back to before the software was installed. You'd think it would tell me what software is actually causing the problem, just like you'd expect the Windows 10 disk to have NOT altered the contents on the hard drive, given that I did not tell it to do anything at all, but not. Oh, and all of my restore points have been removed. Googling the problem shows that it's not exactly uncommon, but mostly it's people who dual boot both Windows 7 and Windows 10, and the working solution there is to apparently turn off fast boot in Windows 10, but since I don't have Windows 10 on this desktop (and really really don't want it), then that's not an option for me. I can create new System Restore points (but of course there are none from before I booted the Windows 10 USB stick), but I can't stop CHKDSK from trying to run at boot up, and MUCH more importantly, I can't get CHKDSK to successfully scan the C: drive even when I deliberately tell it to in Windows, then of course it schedules CHKDSK for the next reboot, but on reboot CHKDSK just gives the same error as when it always tries on bootup without my telling it to. Using: fsutil dirty query c: says "Volume - C: is dirty" And via REGEDIT, at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager Then 'BootExecute' contains: autocheck autochk * Any ideas, please?
  • Create New...