[SOLVED] Review/Repair

latitude64 · May 4, 2024

WIN7 SP1 w/OFFICE ENTERPRISE 2007 - x64 DELL Latitude E6400 :: My browser froze when trying to access a website's email link. iexplore.exe began highlighting in blue as "suspended" over and over again in Task Manager processes. When terminated, it would return again and again as "suspended" as long as Win7 was running. I had a blank screen when trying to access features to turn IE off. I did two restore points, and an image restore from around Oct. of last year. The suspended iexplore persisted, but I had access to the windows features from the image restore. I deleted MS EDGE browser, turned off Internet Explorer in features, and that ended the continual listing of the suspending process of iexplore.exe.
I ran SFC and DISM commands that I was finding autochk.exe and display.dll.mui were corrupted in the STORE also, as well as multiple "fail" errors in opening update packages, or wrong package versions (see CBS log).
I have run a Trend Micro anti-virus full length scan and found no virus for which I was anticipating the autochk.exe as a Trojan. I also ran the following after running the SUR tool:

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows 7 SP1 x64 (6.1.7601)
Start time: 2024-05-03T23:16:38
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 65171
Number of values: 144063

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

==== Warnings ====
None

...and lastly, I did a final SFC that you will note for the last entry of the CBS log. (one of the CBSPersist.log files was removed from the ZIP file so that it would fit the uploading limit 30Mb) Win7 appears to be working as it always has - but without IE and EDGE now.

PeterJ · May 4, 2024

Hello,

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download

SFCFix and move the executable to your desktop.
Download the attachment SFCFix.zip and save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt.
Open the file, then copy and paste its content in your next reply.

latitude64 · May 6, 2024

The following is the SFCfix text that has concluded the Review/Repair requested thereof the update forum:

---------------------------------------------------------------------------------------------
SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-05-05 04:31:45.807
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\User\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-

display.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f76d5676e7d5a264\Display.dll.mui
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-

autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe

Successfully copied file C:\Users\User\AppData\Local\niemiro\Archive\amd64_microsoft-windows-

display.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f76d5676e7d5a264\Display.dll.mui to C:

\Windows\winsxs\amd64_microsoft-windows-display.resources_31bf3856ad364e35_6.1.7600.16385_en-

us_f76d5676e7d5a264\Display.dll.mui.
Successfully copied file C:\Users\User\AppData\Local\niemiro\Archive\amd64_microsoft-windows-

autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe to C:\Windows

\winsxs\amd64_microsoft-windows-

autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe.

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-

display.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f76d5676e7d5a264\Display.dll.mui
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-

display.resources_31bf3856ad364e35_6.1.7600.16385_en-us_f76d5676e7d5a264\Display.dll.mui
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-

autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-

autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe
PowerCopy:: directive completed successfully.

Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2024-05-05 04:40:47.911
Script hash: m7J5g/g1IYfqfp/zlBDedu3Q+bhXgbml+v3B5UbeoAE=
----------------------EOF-----------------------

This procedure appears to have succeeded very well.

As can be seen in the following scannow, the SFC reports a clean bill of system integrity after the Sysnative niemiro scripted fix was executed.

A current review of the attached CBS log for May 5, 2024 will reveal no error codes, no "failed to open packages", and no corrupted files or STORE catalogs.

I will monitor this repair for a week or two while cleaning files, defrag, and another scannow for integrity before I generate another Image restore backup onto a CD-caddy hard drive to replace the previous image - which was apparently corrupted also.

Are there any objections to deleting most of this folder content - less the current May 5th log data to set this repair activity anew ?

This was a very pleasant experience in getting through this malady.

Thank you sincerely with your assistance PeterJ,

Edward Pascoe; A.S.E.E.T.
USAEUR Cold War Veteran

PeterJ · May 6, 2024

Great, job well done.

Are there any objections to deleting most of this folder content

Removing system files, even log files, is not recommended. They do not consume much disk space in this case so I would keep them. Better safe than sorry.

Should we keep this thread open for the next 2 weeks while you perform some cleanup or can we mark this thread as solved ?

latitude64 · Sunday at 12:53 AM

Yes, we can mark this thread as solved herein.

I kept the CBS files in the log folder as recommended, and made a new image in replacing the old one. This latest SFC is still reporting good heath integrity :

When i get some free time, I most certainly will return to browse this intellegent forum.
Thanks again for the help,
and we'll meet again,
ed

PeterJ · Sunday at 5:17 AM

I'm glad we could help. Thread is marked as solved.

Take care.

Search

Search

[SOLVED] Review/Repair

latitude64

New member

Attachments

PeterJ

Moderator, Windows Update Expert, Security Analyst

Attachments

latitude64

New member

PeterJ

Moderator, Windows Update Expert, Security Analyst

latitude64

New member

PeterJ

Moderator, Windows Update Expert, Security Analyst