• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Solved Unable to refresh or reset PC after Automatic Repair fail


whipcream

New Member
Posts
4
#1
My PC fails to boot into Windows and launches Automatic Repair to attempt to repair Windows. When i try to refresh or reset alway get msg " there is a problem resetting your pc, no changes are made" My PC is preinstalled so no I don't have recovery CD/DVD
Here pics

xrsLiOO.jpg

KhOiCp0.jpg

EDU77UO.jpg

ZTc1GoR.jpg

2g6GfMJ.jpg

rVVsT4K.jpg

SDYZTdP.jpg

UOjse33.jpg
 
Last edited by a moderator:

My Computer

System One

  • OS
    Windows 8

Saltgrass

New Member
Pro User
Posts
1,121
#2
It may take an Automatic Repair several times to complete a repair. If you have allowed it to do that, have you tried any of the Startup Settings on the advanced options to see if you can repair it?

Do you have any idea why it might have gone into the repair mode?

Have you tried doing the Factory Reset procedure for the system?

Edit: When you system does an automatic repair, it is supposed to create a log file called srttrail.txt. This file is located in the directory below. If you can get into the command prompt and navigate to that location, you might be able to copy the file to a flash drive so you could attach it. Maybe it will have some information.

C:\Windows\System32\LogFiles\Srt

If you need to find the drive letter for a flash drive, use diskpart.
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

whipcream

New Member
Posts
4
#3
It may take an Automatic Repair several times to complete a repair. If you have allowed it to do that, have you tried any of the Startup Settings on the advanced options to see if you can repair it?

Do you have any idea why it might have gone into the repair mode?

Have you tried doing the Factory Reset procedure for the system?

You might check the thread below. The poster was in about the same situation as you, but had already reset back to Windows 8.0, thus the additional 450 MB Recovery Partition.

http://www.eightforums.com/general-support/47695-too-many-recovery-partitions.html
I have allowed it to repair BUT always get same as first pic

I have tried option on startup setting to disable anti virus and enable safe mode but don't seem to work at all

About factory reset thing i have no idea how to do that

PS. My Windows is 8 not 8.1

Edit is there anyway i can use recovery im thing in last pic ?
 

My Computer

System One

  • OS
    Windows 8

Saltgrass

New Member
Pro User
Posts
1,121
#4
You might check my first post since I edited it.

The factory options for an ASUS system are probably F9 during boot. Your owner's manual should tell you.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

Saltgrass

New Member
Pro User
Posts
1,121
#5
If you go into the Recovery Command prompt, try running Reagentc /info to see if your Recovery Image is registered. To run the utility from the command prompt, you have to start it from the C:\Windows\System32 folder.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

Saltgrass

New Member
Pro User
Posts
1,121
#7
The OEM option might be using the same Advanced Options. But I suppose using the Reset there does the same thing?

So it would seem the Recovery Image is either not present, or not registered and the reagent /info command mentioned in the earlier post might determine that. If it isn't, I am not sure it can be repaired from the recovery environment. Are you having to sign in when you open the Command Prompt?

It might also be the problem is keeping the Recovery Image from being accessed.. Any previous problems with the system you are aware of?

The SRTTrail.txt appears to be of no help.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB

Saltgrass

New Member
Pro User
Posts
1,121
#9
Thanks, I will keep that in mind for the future. I would not have though your Registry would have been corrupted, but it appears it was.

Windows 7 had a repair option called "Last Known Good" which would replace the registry hives with an earlier version, but it looks like that is not available to the user in Windows 8.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB
#10
Windows 7 had a repair option called "Last Known Good" which would replace the registry hives with an earlier version, but it looks like that is not available to the user in Windows 8.
Not exactly. "Last known good configuration" will only try to use the secondary "Controlset".Usually there will be at least two Controlset in all systems and may more in some systems (Controlset001, Controlset002 etc). Default "Controlset" to be used is determined by the value stored in HKEY_LOCAL_MACHINE\SYSTEM\Select key. When we select "Last known good configuration", secondary controlset will be used. So if the "System" hive file is corrupted, both controlsets will be unavailable - "System Restore" or manual hive file replacement from "Regback" folder will be necessary.

Along with the dumbest decisions by Microsoft to hide shutdown option, bury "Safe Mode" etc, geniuses at Redmond decided that "last known good" is no longer requires as "Windows 8" is never going to be failed to boot. Fortunately we can still enable that option manually.

I Know Better: How to enable the Last Known Good Configuration in Windows 8
 
Last edited:

My Computer

System One

  • OS
    Windows 7

Saltgrass

New Member
Pro User
Posts
1,121
#11
Anshad Edavana;389811 "Last known good configuration" will only try to use the secondary [B said:
"Controlset"[/B].Usually there will be at least two Controlset in all systems and may more in some systems (Controlset001, Controlset002 etc). Default "Controlset" to be used is determined by the value stored in HKEY_LOCAL_MACHINE\SYSTEM\Select key. When we select "Last known good configuration", secondary controlset will be used. So if the "System" hive file is corrupted, both controlsets will be unavailable - "System Restore" or manual hive file replacement from "Regback" folder will be necessary.
You are getting a little too far down in the Weeds for me. The basic reason for Last Know Good was to allow backups for things that are involved in booting your computer. This system was not booting, so the option may have helped the original problem, unless you know the Auto Repair has already tried that.

I would be interested in knowing, when a user cannot access the Reset function during a Repair option, what does deleting the HKLM\System key do to suddenly allow such access? Why was it designed in such a manner, and does it work the same way in Windows 8.1?

Does it behave the same if you have booted into a Recovery Drive, or the Install Media?
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB
#12
The basic reason for Last Know Good was to allow backups for things that are involved in booting your computer. This system was not booting, so the optionmay have helped the original problem, unless you know the Auto Repair has already tried that.
Basically there are five Registry hive files inside "System32\Config" folder. They are SYSTEM, SOFTWARE, DEFAULT, SAM and SECURITY. Upon booting, Windows will read this hive files and build the Registry dynamically depending on the hardware and software configuration of the system. SOFTWARE is the hive file which usually stores all software configurations and SYSTEM will have all hardware and driver related info. Usually SYSTEM will be mounted in the Registry branch HKEY_LOCAL_MACHINE\SYSTEM. Under that branch there will be at least two sub branches named Controlset001 and Controlset002 etc. A control set contains system configuration information such as device drivers and services. Usually Windows will only use either one of the Controlset at a time and the other one will be used a s a backup.

What are Control Sets? What is CurrentControlSet?

For example, if you install a new driver, a configuration information for it will be written under the current Controlset in use - let us say "Controlset001". Suppose If the new driver install crashed your system and when you select "Last Known Good", Windows will read the backup Controlset which doesn't contain the new changes ( in this case "Controlset002" ). Since the backup "Controlset" is not updated with new driver's configuration, usually the system will boot fine so you can troubleshoot the issue.


I would be interested in knowing, when a user cannot access the Reset function during a Repair option, what does deleting the HKLM\System key do to suddenly allow such access? Why was it designed in such a manner, and does it work the same way in Windows 8.1?
As you already know, "Refresh" operation will preserve all installed drivers and modern apps. To do that the process must mount both SYSTEM and SOFTWARE hives and backup software and driver settings. Although "Reset" won't preserve anything, it will also try to mount the hives - may be because "Reset" and 'Refresh" are performed by same tool or "Reset" may trying to read licensing info to preserve activation status.

If one of the hive file is corrupted, the process won't be able to mount them and hence the operation will be failed. If we rename the hive files, "Reset" will skip the hive mounting process and continue the operation.

Sorry if this is confusing. I only barely speak English.
 
Last edited:

My Computer

System One

  • OS
    Windows 7

Saltgrass

New Member
Pro User
Posts
1,121
#13
I would be interested in knowing, when a user cannot access the Reset function during a Repair option, what does deleting the HKLM\System key do to suddenly allow such access? Why was it designed in such a manner, and does it work the same way in Windows 8.1?
As you already know, "Refresh" operation will preserve all installed drivers and modern apps. To do that the process must mount both SYSTEM and SOFTWARE hives and backup software and driver settings. Although "Reset" won't preserve anything, it will also try to mount the hives - may be because "Reset" and 'Refresh" are performed by same tool or "Reset" may trying to read licensing info to preserve activation status.

If one of the hive file is corrupted, the process won't be able to mount them and hence the operation will be failed. If we rename the hive files, "Reset" will skip the hive mounting process and continue the operation.
Thanks for the info, that took some time on your part. But what you say is not confusing, seems to be perfect English.

To me, the requirement to rename the hives is illogical. A Reset should ignore everything and do the Reset requested, especially since it does not need the information to complete the operation. I appreciate the explanation and just will assume it is what it is. As you mentioned, Microsoft seems to have made some design decisions where some situations appear to be unexpected and they neglected to plan for such things.

Thanks again. Whipcream did find a good answer.

Edit: To test I did as the link directs and renamed both the System and Software hives. This was done to see what might happen to the system if a Reset was not performed on the system. As you might expect, the system would not boot after 3 attempts. I went to the Advanced options and did a Startup Repair, which did allow the system to boot normally. The System and Software hives had been replaced.

I suppose this would suggest, if the registry was corrupt in the first place, a Reset may not have been needed. My Srttrails.txt file did determine "Registry is Corrupt" as the problem, which Whipcream's log did not show. I suppose there may have been some other type of corruption in another area... no way to know..
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB