New
#11
File in attachment.
Startup Repair won't work until you confirm the Active partition first is System Reserved or Windows 7 partition. More here forTroubleshooting Windows 7 Failure to Start which includes everything that can be done to start unbootable Win7.
Did you try yet booting into Win7 disk System Recovery Options to run System Restore backward to try to find a working config?
There's a lot more that should have been done before tampering with the registry which may now make repairs impossible.
In particular you can from Disk Command Line enable Built-in Administrator - Enable from WinRE - Windows 7 Forums to see if it will boot and then try creating a new User Account - Create - Windows 7 Help Forums. It seems you did similar but may need the full hidden Admin and it would be good to see if it will itself function.
If not I'd run a full scan with Malwarebytes, AdwCleaner, and ESET Online scanner in Safe Mode with Networking, then again run SFC to see if cleaning up infection will repair System files.
At any time you can rescue your files, or transfer them over to a working User account to use deleting the old one once you're sure you have everything.
I tried all the easy solutions the last couple of days. Had they worked, I wouldn't be here now. As a general rule, I've always figured any computer problem I have someone else has had before. So I have resolutely researched the internet, including the items you referenced, in hopes of finding a solution.
This time, I am stumped. If I couldn't boot at all, I would simply reinstall. But because I can boot to safe mode (where I am now) and because I've spent a lot of time getting my computer the way I like it, I'd rather not. Plus at this point it has become a quest.
I have spend a fair fraction of the last three days trying to understand sentences such as this. Please explain what it means.Startup Repair won't work until you confirm the Active partition first is System Reserved or Windows 7 partition.
Should the Active partition be the (100 MB) System Reserved, or the (vastly larger) Windows 7 partition? You really don't say. Can it be one or the other? Surely it can't be both, and surely it can't be neither. Does it matter which? I ask because after trying most everything else I switched from one to the other, and it neither helped nor hurt any way I could tell.
All I know is that in my other computer it's in the System Reserved.
Had you said......that would have been a sentence I could deal with. So to a sentence likeRepair won't work until you confirm the Active partition first is System ReservedBut by adding that little conjunction, You're telling me...I don't know what.Repair won't work until you confirm the Active partition first is Windows 7 partition.
sfcdetails doesn't look very promising. I will ask for an opinion.
It explains it in Troubleshooting Windows 7 Failure to Start I referred you to for the step:
It also explains it in Startup Repair - Run 3 Separate Times you said you followed. Surely you would have seen this if you'd read either tutorialOn a Legacy install to MBR disk, confirm the Partition Marked Active is the 100mb System Reserved (preferred if you have it) or Windows 7 partition (if you don't), run Startup Repair repeatedly up to 3 separate times with reboots in between each - no matter what it reports. If both the System Active and Win7 partitions are on the same hard drive then unplug all other drives to do these repairs.
On some PC's the Recovery partition or an earlier installed OS used in a Dual Boot will hold the Active flag. If another partition than System Reserved or C holds the Active flag and you know this is how it was set up, then go ahead with the repairs. If not skip to Step 9 to get more help since Win7 will not repair unless the correct partition is Set Active. Only the System partition booting the OS should be marked Active.
You could also ask back at any time in any tutorial or in a post for that purpose.
Last edited by gregrocker; 16 Jul 2015 at 19:24.
Yeah, going to bed in short time :) Sorry, can't help more at this stage, as I don't understand much about fixing sfc corruption (something I want to learn). If it comes to anything I can help with, I will add my comments.
The SFC results are interesting.
You appear to have run SFC /SCANNOW three times, according to the logs - and each time it found and fixed exactly the same errors.
There is obviously something repeatedly causing the same corruption on your machine.
It could be either malware, a registry or system 'cleaner', or the system reverting back to a previous state for some reason.
Here's the error/fix list in full...
I have to admit that I'm not really sure where to go next on this - it's almost unheard of for this type of thing to happen.Code:2015-07-16 16:23:49, Info CSI 000004ac [SR] Repairing 31 (0x000000000000001f) components 2015-07-16 16:23:49, Info CSI 000004ad [SR] Beginning Verify and Repair transaction 2015-07-16 16:23:49, Info CSI 000004af [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-07-16 16:23:49, Info CSI 000004b1 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-07-16 16:23:50, Info CSI 000004b3 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:30{15}]"setupcompat.dll" from store 2015-07-16 16:23:50, Info CSI 000004b5 [SR] Repairing corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\System32\CompatTel\CompliancePlugins"\[l:42{21}]"DVDPlaybackCompat.dll" from store 2015-07-16 16:23:50, Info CSI 000004b7 [SR] Repairing corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\System32\CompatTel\CompliancePlugins"\[l:36{18}]"SBCompatPlugin.dll" from store 2015-07-16 16:23:50, Info CSI 000004b9 [SR] Repairing corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\System32\CompatTel\CompliancePlugins"\[l:30{15}]"TouchCompat.dll" from store 2015-07-16 16:23:50, Info CSI 000004bb [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:20{10}]"DevInv.dll" from store 2015-07-16 16:23:50, Info CSI 000004bd [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:22{11}]"sdbapiu.dll" from store 2015-07-16 16:23:50, Info CSI 000004bf [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:24{12}]"cosquery.dll" from store 2015-07-16 16:23:50, Info CSI 000004c1 [SR] Repairing corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\System32\CompatTel\CompliancePlugins"\[l:42{21}]"MediaCenterCompat.dll" from store 2015-07-16 16:23:50, Info CSI 000004c3 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:32{16}]"compatplugin.dll" from store 2015-07-16 16:23:50, Info CSI 000004c5 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:28{14}]"compatctrl.dll" from store 2015-07-16 16:23:50, Info CSI 000004c7 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:22{11}]"wdscore.dll" from store 2015-07-16 16:23:50, Info CSI 000004c9 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:28{14}]"generaltel.dll" from store 2015-07-16 16:23:50, Info CSI 000004cb [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:16{8}]"wica.dll" from store 2015-07-16 16:23:50, Info CSI 000004cd [SR] Repairing corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\System32\CompatTel\CompliancePlugins"\[l:40{20}]"GadgetCompliance.dll" from store 2015-07-16 16:23:50, Info CSI 000004cf [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-07-16 16:23:50, Info CSI 000004d0 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR" 2015-07-16 16:23:50, Info CSI 000004d2 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-07-16 16:23:50, Info CSI 000004d3 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR" 2015-07-16 16:23:50, Info CSI 000004d6 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"wintrust.dll" from store 2015-07-16 16:23:50, Info CSI 000004d8 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"crypt32.dll.mui" from store 2015-07-16 16:23:50, Info CSI 000004da [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:26{13}]"sysmain64.sdb" from store 2015-07-16 16:23:50, Info CSI 000004dc [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:26{13}]"sysmain32.sdb" from store 2015-07-16 16:23:50, Info CSI 000004de [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:40{20}]"sysmain32runtime.sdb" from store 2015-07-16 16:23:50, Info CSI 000004e0 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:26{13}]"drvmain64.sdb" from store 2015-07-16 16:23:50, Info CSI 000004e2 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:26{13}]"drvmain32.sdb" from store 2015-07-16 16:23:50, Info CSI 000004e4 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:40{20}]"sysmain64runtime.sdb" from store 2015-07-16 16:23:50, Info CSI 000004e6 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"invagent.dll" from store 2015-07-16 16:23:50, Info CSI 000004e8 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:30{15}]"vhdprovider.dll" from store 2015-07-16 16:23:50, Info CSI 000004ea [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:30{15}]"logprovider.dll" from store 2015-07-16 16:23:50, Info CSI 000004ec [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\appraiser"\[l:24{12}]"hwcompat.txt" from store 2015-07-16 16:23:50, Info CSI 000004ee [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:28{14}]"dismcoreps.dll" from store 2015-07-16 16:23:50, Info CSI 000004f0 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:38{19}]"imagingprovider.dll" from store 2015-07-16 16:23:50, Info CSI 000004f2 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:22{11}]"dismapi.dll" from store 2015-07-16 16:23:50, Info CSI 000004f4 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:30{15}]"acmigration.dll" from store 2015-07-16 16:23:50, Info CSI 000004f6 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:24{12}]"dismprov.dll" from store 2015-07-16 16:23:50, Info CSI 000004f8 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:24{12}]"dismcore.dll" from store 2015-07-16 16:23:50, Info CSI 000004fa [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"devinv.dll" from store 2015-07-16 16:23:50, Info CSI 000004fc [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:30{15}]"wimprovider.dll" from store 2015-07-16 16:23:50, Info CSI 000004fe [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:36{18}]"folderprovider.dll" from store 2015-07-16 16:23:50, Info CSI 00000500 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:30{15}]"ffuprovider.dll" from store 2015-07-16 16:23:50, Info CSI 00000502 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\apppatch"\[l:22{11}]"frxmain.sdb" from store 2015-07-16 16:23:50, Info CSI 00000504 [SR] Repairing corrupted file [ml:58{29},l:56{28}]"\??\C:\Windows\system32\wbem"\[l:18{9}]"aeinv.mof" from store 2015-07-16 16:23:50, Info CSI 00000506 [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:36{18}]"compatprovider.dll" from store 2015-07-16 16:23:50, Info CSI 00000508 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:26{13}]"appraiser.dll" from store 2015-07-16 16:23:50, Info CSI 0000050a [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\appraiser"\[l:26{13}]"appraiser.sdb" from store 2015-07-16 16:23:50, Info CSI 0000050c [SR] Repairing corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\System32\CompatTel"\[l:26{13}]"diagtrack.dll" from store 2015-07-16 16:23:50, Info CSI 0000050f [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:34{17}]"wu.upgrade.ps.dll" from store 2015-07-16 16:23:50, Info CSI 00000511 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:26{13}]"wuapi.dll.mui" from store 2015-07-16 16:23:50, Info CSI 00000513 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"wuapi.dll" from store 2015-07-16 16:23:50, Info CSI 00000515 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:16{8}]"wups.dll" from store 2015-07-16 16:23:50, Info CSI 00000517 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"wudriver.dll" from store 2015-07-16 16:23:51, Info CSI 00000519 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"wintrust.dll" from store 2015-07-16 16:23:51, Info CSI 0000051b [SR] Repairing corrupted file [ml:520{260},l:56{28}]"\??\C:\Windows\Migration\WTR"\[l:20{10}]"GWXMig.inf" from store 2015-07-16 16:23:51, Info CSI 0000051d [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:18{9}]"GWXUX.exe" from store 2015-07-16 16:23:51, Info CSI 0000051f [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:30{15}]"GWXUXWorker.exe" from store 2015-07-16 16:23:51, Info CSI 00000521 [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:18{9}]"GWXUI.dll" from store 2015-07-16 16:23:51, Info CSI 00000523 [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:40{20}]"GWXConfigManager.exe" from store 2015-07-16 16:23:51, Info CSI 00000525 [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:14{7}]"GWX.exe" from store 2015-07-16 16:23:51, Info CSI 00000527 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:26{13}]"wuapi.dll.mui" from store 2015-07-16 16:23:51, Info CSI 00000529 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:18{9}]"wuapi.dll" from store 2015-07-16 16:23:51, Info CSI 0000052b [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:16{8}]"wups.dll" from store 2015-07-16 16:23:51, Info CSI 0000052d [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"wudriver.dll" from store 2015-07-16 16:23:51, Info CSI 0000052f [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"crypt32.dll" from store 2015-07-16 16:23:51, Info CSI 00000531 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"crypt32.dll" from store 2015-07-16 16:23:51, Info CSI 00000533 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:30{15}]"wuaueng.dll.mui" from store 2015-07-16 16:23:51, Info CSI 00000535 [SR] Repairing corrupted file [ml:56{28},l:54{27}]"\??\C:\Windows\SysWOW64\GWX"\[l:14{7}]"GWX.exe" from store 2015-07-16 16:23:51, Info CSI 00000537 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"aeinv.dll" from store 2015-07-16 16:23:51, Info CSI 00000539 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"aepdu.dll" from store 2015-07-16 16:23:51, Info CSI 0000053a [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:20{10}]"config.xml" from store 2015-07-16 16:23:51, Info CSI 0000053c [SR] Repairing corrupted file [ml:520{260},l:54{27}]"\??\C:\Windows\System32\GWX"\[l:20{10}]"config.cat" from store 2015-07-16 16:23:51, Info CSI 0000053e [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:30{15}]"wucltux.dll.mui" from store 2015-07-16 16:23:51, Info CSI 00000540 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"cryptsvc.dll" from store 2015-07-16 16:23:51, Info CSI 00000542 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"cryptsvc.dll" from store 2015-07-16 16:23:51, Info CSI 00000544 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"wuaueng.dll" from store 2015-07-16 16:23:51, Info CSI 00000546 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"wuauclt.exe" from store 2015-07-16 16:23:51, Info CSI 00000548 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"wups2.dll" from store 2015-07-16 16:23:52, Info CSI 0000054a [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:18{9}]"wuapp.exe" from store 2015-07-16 16:23:52, Info CSI 0000054c [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wuwebv.dll" from store 2015-07-16 16:23:52, Info CSI 0000054e [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:28{14}]"WinSetupUI.dll" from store 2015-07-16 16:23:52, Info CSI 00000550 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"wucltux.dll" from store 2015-07-16 16:23:52, Info CSI 00000552 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"cryptnet.dll" from store 2015-07-16 16:23:52, Info CSI 00000554 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"cryptnet.dll" from store 2015-07-16 16:23:52, Info CSI 00000556 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:30{15}]"crypt32.dll.mui" from store 2015-07-16 16:23:52, Info CSI 00000558 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:50{25}]"mcupdate_GenuineIntel.dll" from store 2015-07-16 16:23:52, Info CSI 0000055a [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:18{9}]"wuapp.exe" from store 2015-07-16 16:23:52, Info CSI 0000055c [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"wuwebv.dll" from store 2015-07-16 16:23:52, Info CSI 0000055e [SR] Repair complete
If you can stop the reversions, then SFC has done its job, since the remaining errors after the scan are only the standard ones from KB3068708 which can be ignored.
Noel, thank you for your time and thoughtful consideration.
Long version of what happened.
All this started when I tired to create a dual boot system, Win 7 & 8.1 (The ultimate plan was to upgrade 8.1 to 10, having a new system to tinker with while keeping my trusty and reliable 7 in place.) I thought the simplest thing would be to put operating systems in two separate physical drives, and then use BIOS to select the appropriate boot drive.
The first time I tried this it worked pretty well. The second time 8.1 went through a series of updates, as it does because it was a new install. When that was all done, Windows 7 wouldn't boot up. I forget now exactly what it did, but what it didn't do was work.
I first tried using system repair from the Windows 7 installation disk. This did some good. Start up found some things to repair. The result was to put me where I am now; 7 goes to the Welcome screen and offers me my user profile icon. When I click on the icon, the screen briefly goes black, then comes back with the spinning Windows circle and the words "logging off." Then it goes back to the welcome screen.
Since then I've tried everything under the sun to try to fix it, including those things suggested by your Greg Rocker.
This is useful insight. Malware is always a possibility. I have run Microsoft Security Essentials, Malwarebytes and Combofix. No help.There is obviously something repeatedly causing the same corruption on your machine.
It could be either malware, a registry or system 'cleaner', or the system reverting back to a previous state for some reason.
I can boot to Safe Mode. All I've been able to find about Safe Mode are sentences such as "Safe mode starts Windows with a limited set of files and drivers." What specifically is the difference between safe mode and normal mode? Is is logical to assume that my troubles lie somewhere in that difference?
The registry may another place to look.
One of the things I tried was this => https://support.microsoft.com/en-us/kb/555648
when Microsoft says...
...they don't literally mean "X:" do they? I changed it to "C:\windows\system32\userinit.exe," Since that time the registry value has changed to "userinit.exe,"Edit these values and type the correct path of shell :
Shell = explorer.exe
Userinit= X:\windows\system32\userinit.exe,
Also in the registry there are several references to "E:\userinit.exe" should these be changed and/or deleted?
Thanks again for your help; I come as a technological pilgrim, seeking enlightenment and redemption.