I do not know if what I did previously helped in any way, they were just suggestions I collated from my scouring boards in which users claimed it helped with a blurred no password prompt login screen.Īnother thing I did before all this as I said was to run chkdsk on the C: boot drive, & disable all non essential windows services & apps (msconfig), also disable all startup programs (task manager). Use PCUnlocker Enterprise to make my old user local account log in automatically without use of login screen - this finally worked. Re-Create my old local user account & assigning it to the Administrators group (didn't work) Make Administrator account visible & activated using command line (didn't work) Use command line to delete all windows system & local caches (didn't work) I managed to get back into my Windows main HDD system - I have no precise idea how, these are the steps I took:
Since the last command failed, is there a point in running sfc / scannow again? So the question is where is the source file - I did change the policy so it will use windows update as source, but it does not seem to comply.
The DISM log file can be found at C:\windows\Logs\DISM\dism.log For more information on specifying a source location, see. Use the "Source" option to specify the location of the files that are required to restore the feature.
The component store is repairable.Ĭ:\windows\system32>dism /online /cleanup-image /restorehealth Ĭ:\windows\system32>dism /online /cleanup-image /scanhealthĭeployment Image Servicing and Management tool
In the new thread post images or share links (one drive, drop box, or google drive) with these commands and results:ĭism /online /cleanup-image /restorehealth For example C:\Windows\Logs\CBS\CBS.log.īackground - cloned a mbr with uefi bootloader from a sata hard disk to a sata ssd disk, had to do some adjusting so bootloader works with bcdboot command line after creating a fat32 esp partition. Windows Resource Protection found corrupt files but was unable to fix some of them.įor online repairs, details are included in the CBS log file located at This process will take some time.īeginning verification phase of system scan. Windows in this scenario will not allow an in place upgrade using windows 21H1 setup iso giving the usual lame reason of unusual uefi configuration.Īll the Dism advice to fix Windows 10 21H1 failed for me apart from these two used consecutively:ĭism.exe /Online /Cleanup-Image /AnalyzeComponentStoreĭism.exe /Online /Cleanup-Image /StartComponentCleanupīeginning system scan. Was advised to create a new thread for my issues trying to repair a hybrid mbr/uefi installation of Windows 10 updated up to 21H1 through windows update.
0 kommentar(er)
