Author Topic: Using for firstime  (Read 5048 times)

0 Members and 1 Guest are viewing this topic.

Offline select21

  • Newbie
  • *
  • Join Date: Jul 2021
  • Posts: 1
  • Karma: 0
    • View Profile
Using for firstime
« on: July 06, 2021, 09:57:07 am »
I did all the backups first then rebooted to safe.  I have a HP 64bit that is 4-5 years old. Unfortunately for the repairs I only unchecked those applying to older than Windows 10.

It has been running for 20hrs 45min.  Shows Repairs 8/42 and Regestering 132 file, Mem used 3.65BB.

I don't mind waiting, but is this time normal??

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Using for firstime
« Reply #1 on: July 06, 2021, 01:40:27 pm »
No, that isn't normal - it only takes about 45mins on mine.

Stop the program and open a Command Prompt (Admin) or Powershell (Admin) and enter these cmds -


That is a read only version but should report if there are any bad sectors on the HDD.

If that completes then enter these -

dism /online /cleanup-image /startcomponentcleanup

dism /online /cleanup-image /restorehealth

sfc /scannow

Enter exit to close the cmd window.

These will all take a little while to complete with the first two reporting completed successfully.

The sfc /scannow can either report no integrity violations or that it has repaired all corruption.

Try Windows Repair again after they complete.

If the chkdsk reports kbs in bad sectors then you will need to immediately create a system image in preparation for full failure.

Performing a chkdsk /r may buy you some time so the system will still work, but once sectors start to go bad, they can escalate quite quickly.

Let me know how you get on.

Offline Willy2

  • Hero Member
  • *****
  • Join Date: Oct 2011
  • Posts: 1165
  • Karma: 18
    • View Profile
Re: Using for firstime
« Reply #2 on: July 08, 2021, 02:37:27 am »
- What's the number of the repair the program got stuck ?