W7 SP1 file system corruption

[Gavin]

This is my first post and I must say after reading technical and in-depth replies WRT corruption etc I’ve come away impressed.

In advance, I’d like to thank you for any help you can offer me.

Although over the past 15 years or so I haven’t read much about what’s relevant WRT computer hardware and software, except what is relevant to my current machine and set up, I’m not a newbie, just a bit rusty. I know up to W7 SP1, but I don’t know anything about servers or LINUX. However, these past months, has got me up to speed somewhat in computer hardware and software. And now that I’ve fixed my protracted .NET Framework issue, I’ve been able to install and/or update more software or newer versions of what I already had/have.


It’s only been while researching building my son a super gaming machine have I, over the past 2 months, have started to look at computer hardware and software again.

It’s 2025 and I’m on W7 SP1. Up until this week, I’ve been able to update W7 SP1 from updates stuck at 2019 to all current updates to 2020. For considerable time I’ve had a protracted .NET framework and Windows Update issue.

Now that these two problems are sorted, I need your expertise regarding file system corruption found using SFC /SCANNOW.

A Google search lead me to Sysnative. It’s a great forum full of experts who know their stuff WRT the intricacies of Windows repair etc. I’ve inquisitively read your solutions regarding file system corruption and I was almost able to fix it myself. The reason why I need to fix my machines file system corruption is because I’m forgoing my new build so that I can build my son a $4000 (excluding peripherals) gaming PC monster. Consequently, I need my 15 year old machine to keep going for another year at least.

I’ve been feeling more and more uneasy using my W7 SP1 machine online, especially when having to log into sensitive sites. And especially, while it wouldn’t update past 2019 and I could clearly see that their were updates still available up until 2020. Chrome stopped supporting W7 SP1 from 110 onwards. I’m stuck on 109 while Chrome is now at version 138. With the .NET Framework and Windows Update issues fixed, it’s the most secure it can ever be on W7 SP1. I’ve always been security consciousness and I’ve never been infected with anything. Even GRC.com’s scanning reports remark on my machines unfathomable super hardening. This current setup is based on many years of tweak/hacks WRT registry, services and using programs such as EMET 5.5 and so forth. The problem I have now is that these tweaks/hacks are a distant memory so I was hoping to carry them over by way of a Windows 10 Enterprise LTSC upgrade rather than a clean install. However, I’m sure a clean install is best and I shall defer to you. I think I will go clean install.

I know I pushing my luck and software I rely on is many versions out of date, or was, from where they are today thanks to the .NET Framework fix. Yet much of the software I rely on has stopped being supported so they are many versions behind what they could be on W10. From a security point of view, I don’t want to chance my luck for another year on W7 SP1.

My machine is 15 years old and the BIOS is dated 2010. I have DDR2 4GB (I’m doubling this to 8GB), CPU is an Intel Dual-Core 2 Duo E8600, and I have a SCSI storage subsystem using LSI adapter and a Seagate 136GB 10K enterprise HDD. For backups, I have 4 internal 4TB SATA HDDs and 4 external HDDs. I was going to dump the SCSI and go with a SSD option just to make it a bit more sprightly.

Therefore, I was thinking of going to the lightest version of Windows 10 Enterprise LTSC. I’d like to get the file system corruption sorted before migrating to Windows 10 Enterprise to mitigate any upgrading complications. I may just do a clean install but I think I would like to try the upgrade route first and see how it goes.

Before I explain my file system corruption, knowing my machine is low spec in today’s standards, should I go Windows 10 Enterprise LTSC? If so, do I go with the non-IoT or IoT version? I know they are binary equivalent. If this means there is no difference between them, why would anyone choose non-IoT over IoT? I know 10 Enterprise non-IoT has end of support (EOS) of 2027 and IoT EOS of 2032. I’m hoping to have the funds for my new machine in the next year so I’m not worried about pushing this machines that far. So which version of Windows and which variant is the question. I have no knowledge of LINUX or anything besides Microsoft Windows.

The biggest failing I’ve found with Windows over the past 25 years is its inability to repair itself. Two lifelines have been Safe Mode (SM) and Last Known Good Configuration (LKGC). Other than that, a regular image to revert to seems to be the best lifeline.

I’ve followed your instructions from here: Windows Update Forum Posting Instructions

Windows Update Forum Posting Instructions


I’ve carried out stages 1-3.

SFC /SCANNOW

SURT (2017)

Components Scanner 1.5.1.0

I’ve uploaded unaltered logs. Please see .rar file ‘CBS+CheckSUR+ComponentsScanner_Logs’.


I’ve read elsewhere about SFCFix Utility 3.0.2.1. It’s not part of the instructions but would you like me to run SFCFix Utility. Shall I just run it now, even after the other tests have run?

I’ve used SURT (2017) over SURT (2014), as it has undergone 5 further updates.

SURT (2017) - Windows6.1-KB947821-v12-x64 (325MB)

Thank you for any help.

​

 

[Windows Update Bot]

Hi @Gavin,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[PeterJ]

Hello and welcome,

Thanks for your detailed introduction.
I will only deal with Windows Update issues in this thread. For other answers to your questions you may start a new thread in another forum section when we are done here.

Some system files are corrupt and need to be replaced.

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.
• Attach that file to your next reply.

 

[Gavin]

Blimey Peter, that was quick :)

Here's my SFCFix results file and it looks good :)

I do have a few questions if that would be ok?

 

[PeterJ]

Great. Please perform a scan with the latest version of the tool SURT:

SURT Scan:

1. Download SURT for your system. (Windows 7 SP1 x64)
2. Once downloaded, execute the installer, and go through the installation (this process can take around 15-20 minutes).
3. On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log.
4. Attach this log to your next reply.

Alternatively, if these instructions are unclear for you, you can follow the tutorial below.
System Update Readiness Tool (SURT)

I do have a few questions if that would be ok?

No problem.

 

[Gavin]

Hey Peter, and thank you for your help.

I carried out SURT using the file you mentioned.

Pre-empting you, on the basis that the CheckSUR was error free, I carried out a SFC /SCANNOW.

It found errors that it couldn't fix.

I’ve enclosed the CheckSUR.log and CBS.log

The first half of the CBS.log is what you had yesterday.

The SURT and SFC scans were carried out today (4th July).

I made sure that AV etc was disabled and services stopped and as many processes ended that I could before carrying out SURT and SFC scans.

All the best

PS: Since taking instruction from you, I haven't carried out a SFCFix Utility (3.0.2.1) scan

 

[PeterJ]

The CheckSur log remains clean which is good. The CBS log shows a newer servicing stack is required before another update can be installed.
No need to run SFCFix for now.


Install Update with DISM

1. Download the update MSU here: http://download.windowsupdate.com/c..._92202202c3dee2f713f67adf6622851b998c6780.msu
2. Copy the MSU file to a convenient location (such as C:\temp).
3. Click on the Start button and in the search box, type Command Prompt
4. When you see Command Prompt on the list, right-click on it and select Run as administrator
5. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   cd C:\temp
   replace C:\temp with your path if different
   
   expand windows6.1-kb4555449-x64_92202202c3dee2f713f67adf6622851b998c6780.msu -f:* C:\temp
   
   DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb4555449-x64.cab
   
   
6. You should receive the message:
   The operation completed successfully.
   Make sure to allow the computer to restart if prompted.
   
7. If you receive any other message:
   Post a screenshot of the Commandprompt window.
   Zip and attach the file C:\Windows\Logs\CBS\CBS.log

 

[Gavin]

Hey Peter

It didn't ask me to restart. So shall I stay in the session I'm in at the moment?

What do you mean by:-

1) The CBS.log shows a newer servicing stack is required

2)...before another update can be installed. (Out of interest, what update?)

It all went as planned with no problems/errors etc. I tried to read the new CBS log entries, but at the moment it's all Greek to me.

CBS.log enclosed

 

[PeterJ]

What do you mean by:-

1) The CBS.log shows a newer servicing stack is required
2)...before another update can be installed. (Out of interest, what update?)

The log shows following line:
"Package "Package_for_KB5001027~31bf3856ad364e35~amd64~~6.1.1.3" requires Servicing Stack v6.1.7601.24554 but current Servicing Stack is v6.1.7601.24544. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]"
So to install KB5001027 the current servicing stack needs to be updated first which we did by installing kb4555449

It all went as planned with no problems/errors etc.

Great. Go ahead and restart the machine.
Check Windows Update again and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Gavin]

Hey Peter

As mentioned before, I carried out your previous instructions, and everything went well using DISM and updating the service stack.

You mentioned restarting the system, which I did later that night and then to do a Windows Update.

It found an Edge 11 security update for 2021, which I installed.

All was going well and the update required me to restart, which I did.

On rebooting, the system was going through the updating phase, but then it got stuck at 67% and then started to revert back. It then booted in to Windows proper.

I went back to Windows Update but it never found the Edge 11 security update again.

Why do I have Edge 11 on my system? As you know, W7 SP1 doesn’t come with Edge 11.

I had .NET Framework and Windows Update issues, which I was able to fix. But before that happened, in my rabbit hole research, the advice mentioned going to the Microsoft Catalogue. It’s only possible to view the page if you have a Microsoft browser. My original W7 SP1 Microsoft browser IE was busted.

So this is the reason why I installed Edge 11 but it was only after your service stack update using DISM etc, that Windows Update had ever shown this Edge 11 security update of 2021. As mentioned, I’ve tried Windows Update a few times since last night and every time it no longer finds this Edge 11 security update.

I tried to update Edge 11 directly to 140 today using the latest installer ‘MicrosoftEdgeEnterpriseX64’. I idea being that maybe once this latest installer of Edge 11 was installed not only would the Edge 11 security update of 2021 likely be superseded but if there were any updates to it or required other updates too, Windows Update would find them.

But the Edge 11 installer failed with the message:


Microsoft Edge error
A program ran as part of the setup did not finish as expected. Contact your support personnel or package vendor.


Prior to the failed install of Edge 11, my Edge 11 was at 88, but after I rebooted, it was now version 109.0.1518140 (Official build) (64-bit) even after the failed Edge 11 latest installation. Which coincidentally is where Chrome is stuck on 109. And as both Edge and Chrome are based on the Open Source of Chromium this may be the reason they both show version 109.

I’ve enclosed my cbs.log

All the best

 

[PeterJ]

the advice mentioned going to the Microsoft Catalogue. It’s only possible to view the page if you have a Microsoft browser.

You can browse the website Microsoft Update Catalog with Mozilla Firefox and Google Chrome also.
If IE is broken install Firefox or Chrome and use that. Don't use Edge and because Edge wasn't installed properly, don't install updates for Edge.

The Servicing Stack update was installed successfully.
We don't need KB5001027 as long as Edge isn't installed correctly.

 

[Gavin]

Hey Peter

I've uninstalled Edge 11

But I received this error message, which I used to get pre-Edge 11.



iexplorer.exe - Application Error

The exception unknown software exception (0xc0000409)
occurred in the application at location 0x00081084

Click on OK to terminate the program



I have been using Chrome but it has stopped at v109 as W7 SP1 is no longer supported. Chrome is now at v138.


All the best

 

[PeterJ]

I have been using Chrome but it has stopped at v109 as W7 SP1 is no longer supported. Chrome is now at v138.

I know but it will give you the option to browse the internet with this machine. Firefox is also no longer supported, stuck on v115 for Windows 7 but still gets minor updates.

explorer.exe - Application Error

The exception unknown software exception (0xc0000409)
occurred in the application at location 0x00081084

We need to look further on your machine.

FRST Scan:

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
2. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
4. Press the Scan button.
5. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
6. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[Gavin]

Some good news and progress Peter

Once I uninstalled Edge 11, I rebooted.


I executed 'iexplorer.exe' residing on W7 SP1, at


C:\Program Files\Internet Explorer\iexplorer.exe


And I received the same Application Error message I sent you earlier. Damn I thought.


But as I clicked on 'iexplorer.exe' , I received a pop-up message from the system tray of Microsoft EMET 5.52. It said:



'EMET detected EAF mitigation and will close the application: iexplorer.exe'



So I wrote, "Do you think it would make sense to uninstall EMET 5.52, especially as it is no longer supported and is an aggressive program? Especially while trying to understand the problems with my system and wanting to upgrade to W10 Enterprise once my system is in the best possible health? It may be the route cause. I cannot say for sure but what do you think WRT uninstalling EMET?"

After I wrote the above, I thought, instead of uninstalling EMET, do it gradually, so I unticked everything for 'iexplorer.exe' to see what would happen and then to ascertain what may be causing me issues for 'iexplorer.exe' and may be other current issues also. I thought EMET 5.52 may be a good place to start with testing. Using it to tease out and replicate known problems and then finding the perfect resolution.

The other programs within EMET have been uninstalled a very long time ago, so it may be worth unticking these all too. And if there are no issues, think about uninstalling EMET altogether. I think that as 'iexplorer.exe' is the only program under EMET's dominion and the only program that was causing me problems and now found to be because of EMET, what do you think about uninstalling EMET? I think it is past its sell-by-date.

Anyway, I went in to the settings of EMET (see image) and I unticked everything for ‘iexplorer.exe’ and now I.E. works


PS: I've narrowed down the errant configuration. Everything else can be ticked except 'EAF' as mentioned in the EMET mitigation popup message. So that's definitely the fix.

 

[PeterJ]

Great job.
Run the command Dism /Online /Cleanup-Image /CheckHealth in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[Gavin]

Hey Peter

I received:


Error 87
The checkhealth option is not recognized in this context. For more information, refer to the help.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


I've enclosed both CBS and DISM logs.


A cursory look online, as I had done before posting here without success, resulted in the following information:

1) DISM error 87, "The parameter is incorrect," often arises from syntax errors in the DISM command, such as typos or incorrect spacing. (I know this isn't the case)

2) It can also indicate an issue with the Windows Modules Installer service or the use of unsupported DISM options. (This service was not started in Services.exe so I started it and I still received Error 87)


WRT to Windows Modules Installer service, is that a service that needs to be set to Automatic in Services.exe? I have it set to Manual so it should start if needed.

As a last attempt I tried to execute the DISM command via elevated Windows Powershell, as I have done in the past before posting here, but to no avail.

If you think it is worth unchecking EMET 5.52's program settings one-by-one, I can. I can then uninstall it but I will wait for your instruction on this. For years EMET, has been a blessing, but its tight grip on a system can be a curse also. EMET has only started to reappear in the systemtray after disappearing some time ago. I'm always in services.exe but until these past 2 months I haven't seen it in there either. So I was never aware of the EMET EAF mitigation issue regarding iexplorer.exe, only as a distant memory from years ago. I've just stopped EMET service and EMET has disappeared from the system try. I think I must have seen Microsoft EMET in Services and started it, and then it's resumed in the system tray but haven't reacted to it as it's been quite. I gave up years ago trying to get iexplorer.exe to work. I've just this moment stopped the Microsoft EMET service and EMET has disappeared from the system try. So EMET may be implicated to some degree.

I also checked Windows Update for any updates last night and today and was surprised to see the same Edge security update of 16th March 2021. The information WRT this security update refers to:

When clicking on ‘More Information’ - KB5001027: Update for the new Microsoft Edge for Windows 7 SP1 and Windows 8.1: March 16, 2021 - Microsoft Support

When clicking on ‘Support Information’ - KB5001027: Update for the new Microsoft Edge for Windows 7 SP1 and Windows 8.1: March 16, 2021 - Microsoft Support

 

[Gavin]

Peter, is there anything I need to do WRT.

'Before installing KB4555449, you need to have the SHA-2 update (KB4474419 or later) and the servicing stack update (SSU) (KB4490628 or later) installed.'

 

[PeterJ]

I received:

Error 87
The checkhealth option is not recognized in this context. For more information, refer to the help.

Oops, I made a mistake.Please do following:

Run the command Dism /Online /Cleanup-Image /ScanHealth in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

I also checked Windows Update for any updates last night and today and was surprised to see the same Edge security update of 16th March 2021.

Apparently Edge isn't completely removed causing Windows Update to provide KB5001027. You can ignore this update.

Before installing KB4555449...

This update is already installed.

 

[Gavin]

Hey Peter and I really appreciate your help.

The procedure carried out successfully.

Here is the CBS.log

 

[Gavin]

Here's the DISM.log, Peter.