Windows 10: Windows 10 Home - Repair Loop

Hello.


Short description: Windows 10 Home in an endless "repair mode" loop. This happened on the 30.03.2020 and my guess it, that it has to do with updates from that date.


What I have done yet in the cmd offered by the windows repair system:


I created an bootable USB Drive with the media creation tool from microsoft. However, I could also just boot from the SSD.


I know that the windows installation in on partition "e:\" when I boot from the usb drive or the SSD.


I checked the e:\windows\system32\logfiles\srt\srttrail.txt - I remember there was written something about "error 0x490". However after rebooting the system a lot of times, I cant find this message anymore/log overwritten pretty often. It is just saying that it cant solve any problems with the tests but that there is one problem without saying what


chkdsk /f /r - no problems found

sfc /scannow - "Der Windows Ressourcenschutz hat eine Integritätsverletzung gefunden" which would be something like "The windows ressource protection has found an integrity violation"


----------------------

So, both above didnt help, so I just tried to remove updates with dism. Here is mydism /image:e:\ /e:\scratchdir /get-packages /format:table output:

Tool zur Imageverwaltung fr die Bereitstellung
Version: 10.0.18362.1

Abbildversion: 10.0.18363.693

Paketauflistung:


---------------------------------------------------------------------------------------------------- ----------- --------------- -----------------
Paketidentit„t Status Versionstyp Installationszeit
---------------------------------------------------------------------------------------------------- ----------- --------------- -----------------
Microsoft-OneCore-ApplicationModel-Sync-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.329 Installiert OnDemand Pack 15.09.2019 10:56
Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~de-DE~10.0.18362.693 Installiert Language Pack 30.03.2020 12:39
Microsoft-Windows-FodMetadata-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert Feature Pack 19.03.2019 12:17
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.18362.657 Installiert Foundation 30.03.2020 12:39
Microsoft-Windows-Hello-Face-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Abgel”st OnDemand Pack 19.03.2019 12:16
Microsoft-Windows-Hello-Face-Package~31bf3856ad364e35~amd64~~10.0.18362.628 Installiert OnDemand Pack 17.02.2020 17:12
Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-Basic-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-Handwriting-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-OCR-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-Speech-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-TextToSpeech-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Abgel”st OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-LanguageFeatures-TextToSpeech-de-de-Package~31bf3856ad364e35~amd64~~10.0.18362.387 Installiert OnDemand Pack 17.10.2019 08:02
Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Abgel”st OnDemand Pack 19.03.2019 12:17
Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~~10.0.18362.449 Installiert OnDemand Pack 30.03.2020 12:39
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 23.07.2019 15:36
Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:16
Microsoft-Windows-TabletPCMath-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Installiert OnDemand Pack 19.03.2019 12:16
Microsoft-Windows-Xps-Xps-Viewer-Opt-Package~31bf3856ad364e35~amd64~~10.0.18362.657 Installiert OnDemand Pack 17.02.2020 17:12
OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.1 Abgel”st OnDemand Pack 19.03.2019 12:17
OpenSSH-Client-Package~31bf3856ad364e35~amd64~~10.0.18362.657 Installiert OnDemand Pack 17.02.2020 17:12
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3034 Abgel”st Update 31.10.2019 14:55
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3068 Abgel”st Update 18.12.2019 09:14
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3105 Abgel”st Update 16.01.2020 11:12
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3114 Abgel”st Update 11.02.2020 11:43
Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3143 Installiert Update 04.03.2020 12:50
Package_for_KB4503308~31bf3856ad364e35~amd64~~10.0.1.1 Installiert Security Update 28.07.2019 13:36
Package_for_KB4508433~31bf3856ad364e35~amd64~~18362.263.1.1 Installiert Security Update 15.08.2019 20:56
Package_for_KB4509096~31bf3856ad364e35~amd64~~18362.235.1.0 Installiert Security Update 23.07.2019 16:10
Package_for_KB4515383~31bf3856ad364e35~amd64~~18362.350.1.0 Installiert Security Update 12.09.2019 10:20
Package_for_KB4516115~31bf3856ad364e35~amd64~~10.0.1.0 Installiert Security Update 15.09.2019 10:56
Package_for_KB4517245~31bf3856ad364e35~amd64~~10.0.1.5 Installiert Update 23.01.2020 13:31
Package_for_KB4521863~31bf3856ad364e35~amd64~~18362.411.1.3 Installiert Security Update 16.10.2019 12:48
Package_for_KB4524569~31bf3856ad364e35~amd64~~18362.471.1.1 Installiert Security Update 13.11.2019 11:13
Package_for_KB4525419~31bf3856ad364e35~amd64~~18362.447.1.2 Installiert Security Update 31.10.2019 14:58
Package_for_KB4528759~31bf3856ad364e35~amd64~~18362.590.1.0 Installiert Security Update 16.01.2020 09:03
Package_for_KB4537759~31bf3856ad364e35~amd64~~10.0.1.0 Installiert Security Update 17.02.2020 17:12
Package_for_KB4538674~31bf3856ad364e35~amd64~~18362.651.1.0 Installiert Security Update 15.02.2020 12:26
Package_for_KB4541338~31bf3856ad364e35~amd64~~18362.710.1.0 Installiert Security Update 11.03.2020 07:45
Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.693.1.7 Installiert Update 30.03.2020 12:39

Der Vorgang wurde erfolgreich beendet.


I wanted to remove all the packages that are installed on the 30.03.2020 to see if that will solve the problem, however ...

When I try to remove one update like this:


dism /image:e:\ /scratchdir:e:\ /remove-package /packagenameackage_for_RollupFix~31bf3856ad364e35~amd64~~18362.693.1.7 /norestart


I get an error message. Error: 0x800f082f


Can I somehow manually install and then remove those updates again? Because I couldnt find "RollupFix~31bf3856ad364e35~amd64~~18362.693.1.7" on the microsoft site as an update i.e.

:)

 

Windows 10 Repair Boot Loop

Hi Jed,

If your computer is stuck in a boot-loop state of Windows, it could mean that automatic repair isn't able to repair a corrupted or broken system file, but attempts to repair it over and over again. For us to assist you properly in resolving this boot-loop
state, kindly respond to the questions below:

• Did the issue occur even after removing the USB wireless mouse?
• Aside from running DISM, what other troubleshooting steps have you done? This is for us to know and to avoid any duplication of efforts on your end.

We look forward to your response.

 

Automatic Repair Loop

Hi Charlene,

Your concern regarding the device going into an Automatic Repair Loop can be caused by change on its settings/configuration or broken system files. To effectively assist you with your concern, can confirm if you've made any changes on your device prior to
your concern?

As an initial step to get back into the normal Windows screen, we suggest that you perform a
Startup repair. The repair will attempt to fix any broken components/files which may prevent your device from booting properly. To do this, follow the steps below:

• On theAutomatic Repair screen, select Advanced options.
• Select Troubleshoot.
• Select Advanced options.
• Select Startup Repair.

We'll appreciate if you can send us an update.

 

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.**