Windows 10: Windows 10 repairing device every time I startup the pc

When I turn it on it launches the startup repair process, and will fail every time, along with creating a log that I will post later on. If I click on 'use another operating system installed' and then select 'Windows 10 Home' then the device will work properly with no issues at all. I've checked the event viewer, virus/malware scans, updating my drives and everything else. Alongside this, My disk tray keeps opening on startup too. I also recently changed my motherboard due to issues with it and needed to re-install the system files from a USB I made The files on my pc were not removed.


Here are the logs that were created:

setuperr


2019-12-28 14:36:38, Error Failed to check OS architecture. 0x00000490[gle=0x00000002]

2019-12-28 14:36:38, Error [recenv.exe] winreArePathsEqualFailed to get attributes for E:\WINDOWS: 0x2

2019-12-28 14:36:38, Error WinReGetConfigEx failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Error CRecoveryToolAction->Init failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Error WinReGetConfigEx failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Error CRecoveryToolAction->Init failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:39, Error Invalid path specified


setupact


2019-12-28 14:36:38, Info Starting enumeration of PnP devices.

2019-12-28 14:36:38, Error Failed to check OS architecture. 0x00000490[gle=0x00000002]

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReIsWimBootEnabled

2019-12-28 14:36:38, Info [recenv.exe] Parameters: pszWinDir: E:\WINDOWS

2019-12-28 14:36:38, Error [recenv.exe] winreArePathsEqualFailed to get attributes for E:\WINDOWS: 0x2

2019-12-28 14:36:38, Warning [recenv.exe] Failed to check whether X:\windows is the current Windows directory

2019-12-28 14:36:38, Info [recenv.exe] RegLoadKey $OFFLINE$SYSTEM failed. Error: 0x3.

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReIsWimBootEnabled returns 0 with last error: 0x0

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReGetConfig

2019-12-28 14:36:38, Info [recenv.exe] Parameters: configWinDir: NULL

2019-12-28 14:36:38, Info [recenv.exe] WinRE config file path: E:\WINDOWS\system32\Recovery\ReAgent.xml

2019-12-28 14:36:38, Warning [recenv.exe] read xml file E:\WINDOWS\system32\Recovery\ReAgent.xml failed: 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentXMLParser:arseConfigFile failed to read config xml file 0x3 in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 779

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentXMLParser:arseConfigFile xml file: E:\WINDOWS\system32\Recovery\ReAgent.xml returning 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentConfig:arseConfigFile returned with 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentConfig::Init failed to init reagent xml parser 0x3 in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 1916

2019-12-28 14:36:38, Warning [recenv.exe] WinReGetConfigInternal failed to init agent config 0x3 in file base\diagnosis\srt\reagent2\reinfo\shared.cpp line 162

2019-12-28 14:36:38, Warning [recenv.exe] winre get config failed with error code 0x3

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReGetConfig return value: 0, last error: 0x3

2019-12-28 14:36:38, Error WinReGetConfigEx failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Error CRecoveryToolAction->Init failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReGetConfig

2019-12-28 14:36:38, Info [recenv.exe] Parameters: configWinDir: NULL

2019-12-28 14:36:38, Info [recenv.exe] WinRE config file path: E:\WINDOWS\system32\Recovery\ReAgent.xml

2019-12-28 14:36:38, Warning [recenv.exe] read xml file E:\WINDOWS\system32\Recovery\ReAgent.xml failed: 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentXMLParser:arseConfigFile failed to read config xml file 0x3 in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 779

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentXMLParser:arseConfigFile xml file: E:\WINDOWS\system32\Recovery\ReAgent.xml returning 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentConfig:arseConfigFile returned with 0x3

2019-12-28 14:36:38, Warning [recenv.exe] ReAgentConfig::Init failed to init reagent xml parser 0x3 in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 1916

2019-12-28 14:36:38, Warning [recenv.exe] WinReGetConfigInternal failed to init agent config 0x3 in file base\diagnosis\srt\reagent2\reinfo\shared.cpp line 162

2019-12-28 14:36:38, Warning [recenv.exe] winre get config failed with error code 0x3

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReGetConfig return value: 0, last error: 0x3

2019-12-28 14:36:38, Error WinReGetConfigEx failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Error CRecoveryToolAction->Init failed. Error: 0x00000003[gle=0x00000003]

2019-12-28 14:36:38, Info Invalid launch type for OEM-Front-End, 0x4

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReGetConfig

2019-12-28 14:36:38, Info [recenv.exe] Parameters: configWinDir: NULL

2019-12-28 14:36:38, Info [recenv.exe] Using recovery file at \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] WinRE config file path: \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] Update enhanced config info is enabled.

2019-12-28 14:36:38, Info [recenv.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo In WinPE Using winre guid from the config file

2019-12-28 14:36:38, Info [recenv.exe] WinRE is installed

2019-12-28 14:36:38, Info [recenv.exe] WinRE is installed at: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE

2019-12-28 14:36:38, Info [recenv.exe] System is WimBoot: FALSE

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReGetConfig return value: 1, last error: 0x0

2019-12-28 14:36:38, Info Auto launch narrator not specified

2019-12-28 14:36:38, Info Custom boot app not specified

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReGetConfig

2019-12-28 14:36:38, Info [recenv.exe] Parameters: configWinDir: NULL

2019-12-28 14:36:38, Info [recenv.exe] Using recovery file at \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] WinRE config file path: \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] Update enhanced config info is enabled.

2019-12-28 14:36:38, Info [recenv.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo In WinPE Using winre guid from the config file

2019-12-28 14:36:38, Info [recenv.exe] WinRE is installed

2019-12-28 14:36:38, Info [recenv.exe] WinRE is installed at: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE

2019-12-28 14:36:38, Info [recenv.exe] System is WimBoot: FALSE

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReGetConfig return value: 1, last error: 0x0

2019-12-28 14:36:38, Info OS volume was not locked or couldn't be processed. Defer unlocking remaining volumes. 0x00000000

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReCreateLogInstanceEx

2019-12-28 14:36:38, Info [recenv.exe] Using recovery file at \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] Update enhanced config info is enabled.

2019-12-28 14:36:38, Info [recenv.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo In WinPE Using winre guid from the config file

2019-12-28 14:36:38, Info [recenv.exe] WinRE is installed

2019-12-28 14:36:38, Info [recenv.exe] Exit WinReCreateLogInstanceEx returns error code 0x0

2019-12-28 14:36:38, Info Finished enumeration of PnP devices.

2019-12-28 14:36:38, Info [recenv.exe] Enter WinReGetConfig

2019-12-28 14:36:38, Info [recenv.exe] Parameters: configWinDir: NULL

2019-12-28 14:36:38, Info [recenv.exe] Using recovery file at \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] WinRE config file path: \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:38, Info [recenv.exe] Update enhanced config info is enabled.

2019-12-28 14:36:38, Info [recenv.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo In WinPE Using winre guid from the config file

2019-12-28 14:36:39, Info [recenv.exe] WinRE is installed

2019-12-28 14:36:39, Info [recenv.exe] WinRE is installed at: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\WindowsRE

2019-12-28 14:36:39, Info [recenv.exe] System is WimBoot: FALSE

2019-12-28 14:36:39, Info [recenv.exe] Exit WinReGetConfig return value: 1, last error: 0x0

2019-12-28 14:36:39, Info Offline scanning application not configured

2019-12-28 14:36:39, Error Invalid path specified

2019-12-28 14:36:39, Info Copying logs from [X:\windows\Logs\RecEnv] to [E:\WINDOWS\Logs\RecEnv_Ramdisk]

2019-12-28 14:36:39, Info [recenv.exe] Enter WinReRestoreLogFiles

2019-12-28 14:36:39, Info [recenv.exe] Using recovery file at \\?\GLOBALROOT\Device\HarddiskVolume3\RECOVERY\WINDOWSRE\ReAgent.xml

2019-12-28 14:36:39, Info [recenv.exe] Update enhanced config info is enabled.

2019-12-28 14:36:39, Info [recenv.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo In WinPE Using winre guid from the config file

2019-12-28 14:36:39, Info [recenv.exe] WinRE is installed

2019-12-28 14:36:39, Info [recenv.exe] Enter WinReSetTriggerFile

2019-12-28 14:36:39, Info [recenv.exe] Parameters: DirName: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\Logs, fDelete: 0

2019-12-28 14:36:39, Info [recenv.exe] Exit WinReSetTriggerFile return error code: 0x0

2019-12-28 14:36:39, Info [recenv.exe] Exit WinReRestoreLogFiles returns 1 with last error: 0x0

2019-12-28 14:36:49, Info Copying logs from [X:\windows\Logs\RecEnv] to [E:\WINDOWS\Logs\RecEnv_Ramdisk]

:)

 

Recovery. Your pc or device needs to be repaired

Hi,

To address your concern, we suggest that you run the Windows Startup repair. To do that, follow these steps:

• Using you installation media, access the Windows recovery environment.
• Select Troubleshoot
• Choose Advanced option
• Choose Automatic Repair or Startup Repair.
• Once done, your system will restart.

Let us know if you need further assistance.

 

Repair Windows 7/8/10

Repairing Windows 8

Further improving on previously deployed OS repair methods, Windows 8, 8.1, Server 2012 and 2012 R2 further allowed advanced repair where an in-place upgrade or total re-install would be required on previous operating systems. In all honesty, before Windows 10 implementation, this was arguably the easiest OS to repair for a couple of years by running more basic commands.

This has since been advanced to more closely match Windows 10/Server 2016 repairs but with the below information I hope to guide you through performing these advanced tasks more easily!

Spoiler: Windows 8/8.1 Repair DISM

If CHKDSK and SFC fail to repair the issues with the system, then it this is your next option and besides restoring from a previous backup might be the second-to-last option before re-installing the operating system. We will utilize DISMfor this next repair option.

• In some instances, you won't need the OS ISO to perform the DISM image cleanup. You can attempt this on any OS from 8-10 by using the following command in elevated CLI: DISM /Online /Cleanup-Image /RestoreHealth
• In many cases now due to some changes Microsoft made, you'll need to have a copy of the OS ISO available. The ISO will need to be a standard deployment variety that contains Install.WIM in the Sources directory, otherwise the process will fail. Once you have the correct ISO, mount it in Explorer (can do this natively on Microsoft Windows 8.0+), verify the drive letter, verify Image.WIM in the Sources directory.
  • To download a Windows 8.1 ISO from Microsoft, click here.
• Enter the following in elevated CLI: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
  • X = drive letter of mounted ISO. Change to match the appropriate drive letter.
  • Say I had the Install.WIM located in C:\Images, I would type the following command: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:C:\Images\Install.WIM:1 /LimitAccess

The DISM scan can take a while, often times longer than an CHKDSK or SFC scan. To speed up the process, have the Image.WIM on a faster flash media or on local storage rather than disc media. This will help greatly. In many cases one or two runs of this command will repair most issues I've found with Windows 8/8.1.

Once the DISM repair process has been found successful, or not, I will perform a reboot. If the repair was unsuccessful, this will be when I attempt a second pass. If the second pass fails, it is time to move onto the next solution.

However, if the DISM repair passes at any point, reboot the system and then perform an SFC to confirm no further issues are found or need resolved. This step is likely overkill for those not seeking to do optional steps.

Operating System Refresh

It should be noted that in the event DISM fails to repair the system, then an OS refresh would be the next suggestion if the deployed that could save the user's files and OS deployment.

This feature has been an available feature since Windows 8 launched in 2012. The biggest benefit with this option over Windows 7's in-place-upgrade is not necessarily requiring the OS installation media to perform the repair.

If the system is an OEM, an OS refresh from the OEM partition may mean a reinstall of the OS and loss of user data but the restoration of OEM software and bloatware. But you can still choose a manual OS-only refresh without the bloatware if you take the correct steps.

The best choice in my opinion is to run an OS refresh procedure from the advanced boot menu or you can run the installation media while in Windows to perform and Upgrade installation, this will keep your files and settings but replace Windows files and components.

To access the advanced boot menu for Windows 8, there are a several options.

• When choosing restart from the OS GUI, hold down SHIFT and click restart. This method will work even if you cannot log into a profile on the system which makes it very useful in some situations.
• If logged in, access PC Settings, and click Restart Now under Advanced Startup.
• If logged in, open a command prompt window and type shutdown /r /o /t 0 which will initiate a reboot into the advanced menu right with no delay. Without /t 0, there will be a 60-second delay. The number value after the /t is delay seconds.

Once you've reached the advanced boot menu, choose Troubleshoot. From there you can choose to Refresh your PC, Reset your PC and Advanced Options. For this repair, we want to choose Refresh your PC. It's description reads "If your PC isn't running well, you can refresh it without losing our files." That is exactly what we want to accomplish here!

Follow the prompts and processes, and after the refresh installation and rebooting, you should be greeted with a login screen back to your profile in your stable OS environment. At this point you should be able to use the system as intended, if in doubt then re-run the SFC and DISM scans.

In-Place Upgrade

If CHKDSK, SFC and DISM fail to repair the issues with the system, yet you can still boot to the Windows desktop, then the next option is to perform an in-place upgrade. This is more in-depth than an Operating System Refresh. It re-installs most of the operating system's core image and critical files without losing your profiles, data or programs, but do expect to lose some settings. In many cases this process can fix some major issues and refresh an otherwise corrupt and issue-ridden OS installation back to something stable and usable.

Time to close the CLI windows and get back into the GUI, unless you want to deploy Windows through CLI. You'll have to source a different guide for that process!

Requirements to perform an in-place upgrade:

• Must have installation media that matches the installed OS version and type. This applies to both Windows and Windows Server.
• Must be able to get to the desktop on the affected system to correctly initiate this process, booting to the media will not allow an upgrade to be performed.

That last rule is the frustrating part of this repair process if you cannot get that far, backup what you can and do a fresh installation. Otherwise proceed.

• Start the process by using autorun or manually running setup.exe from the installation media.
• Windows 8/Server 2012+ can mount ISO's in Windows Explorer, you can use that instead of physical media options to perform this task.
• You'll come to the installation window, the options will be Upgrade or Custom. Choose Upgrade. This is critical as choosing custom will force you to overwrite, append or wipe out the current install rather than performing any kind of repair.
• Follow the on-screen prompts, which should be very few for you to interact with. The overall process looks and is the Windows install GUI. Once it is completed, the system will automatically reboot (may need to more than once).
• After the reboot(s) after the in-place upgrade you should have a fully functional Windows without issues or corruptions.

Performing an in-place upgrade makes sense, and gives you a stable and clean running operating system when there's an issue or corruption you just can't fix but things aren't broken enough to warrant a fresh installation. The point of this process is to refresh the Windows OS files but retain your data, programs, and settings. That is precisely what the in-place upgrade procedure accomplishes.

I should also add that this process can be accomplished remotely as well, from start to finish. I have done so with persistent LogMeIn, ScreenConnect and Teamviewer installations on various remote systems I have performed this task on, RDP should work as well. Being able to do this level of repair remotely is a huge benefit to any sysadmins out there looking to keep a client happy and perform that "remote magic" IT guys are known for.


**If at this point your issues are not fixed, then there is something else occurring that is causing the issue be it Malware, hardware, drivers, etc. Please refer to the OP in this thread to run through some of those tests and diagnostics, or create a new thread seeking help and stating what you've tried.**

 

Windows 10 random automatic repair after changing boot priority.

Hello. So i have an Windows 10 Pro. Sometimes when i am changing in bios boot order from USB to HDD ( SDD ) windows starts booting with AUTOMATIC REPAIR and then restarting. Is this something with BIOS \ Windows 10 bug related? Tested on pc and on laptop , and sometimes it doing the same.


Situation on PC first,listen:

Few days ago after i change boot in UEFI BIOS from USB to SSD.
Then Windows 10 showed at 1 boot Automatic Repair.
When starting Windows 10 boot loader starts by "preparing automatic repair" and diagnosing pc.
Interesting is that if I restart Windows (after procedure mentioned earlier) it will boot normally. This startup problem was occured only when starting system again after shutdown or restarted pc from windows.So i was needed 2 boots to boot properly to windows.
But on pc, format was needed to remove completely issue and after format is fine.

Pc :
2x8gb Kingston Hyperx 1600mhz DDR3
SSD samsung Evo 250 gb
4790k stock
Asus Sabertooth Z97 Mark 2 with UEFI BIOS


Now laptop with old standard bios:
On laptop i made the same operation, change boot from USB to HDD and on first boot Windows 10 shows Automatic Repair. But it happened once and i cant reproduce. No format was needed.

laptop is very old with 2gb ram

Why on pc format was needed when on laptop not?



Thanks for suggestions.