Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows Explorer.exe is corrupt and Windows Update

explorer.exe windows 7 corrupt update

  • Please log in to reply

#1
SophieMayk

SophieMayk

    Member

  • Member
  • PipPip
  • 82 posts

Hello,

 

My partners PC recently started becoming slower and slower, he's had this issue before and I ran the Windows Repair disk to fix all previous problems. It's been about a year and a half since and the same problems are occurring. I noticed error logs reporting that there were bad blocks on his HDD. 

 

Everything became unresponsive regularly for a couple of seconds and then resumes as normal (for example typing in a Word document would freeze and then resume.) So I ran Chkdsk after a reboot and I saw it reporting errors for Explorer.exe and a MSconfig file. The Chkdsk completed and since then have had no reports of bad blocks or freezing problems (computer is running at normal speed again.)

 

Now I am trying to run Windows Update and getting the error "Cannot check for updates as service is not running", I tried the Microsoft Troubleshooter and it stated that it could not fix an error "0x80080005". Other issues were resolved but I'm still unable to update. I tried Googling solutions and none seem to be working. I ran sfc /scannow and saw that it was unable to fix some issues. From what I can see, it is still having issues with Explorer.exe and Microsoft Windows Installer. I have included a small extract from the end of the CBS log and I'm hoping someone may be able to tell me what is going on and how I can fix these issues as I assume they'll just cause more problems over time as well as not being able to Check for Updates*.

 

*edit I have since found how to get Windows Update to work, for some bizarre reason I have to turn off Windows Updates and it seemed to download. I had 18 important updates to install...

 

POQ 158 ends.
2018-05-22 10:19:12, Info                  CSI    0000038c [SR] Verify complete
2018-05-22 10:19:12, Info                  CSI    0000038d [SR] Repairing 2 components
2018-05-22 10:19:12, Info                  CSI    0000038e [SR] Beginning Verify and Repair transaction
2018-05-22 10:19:12, Info                  CSI    0000038f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7601.23537_none_b0517adca98752cc\explorer.exe do not match actual file [l:24{12}]"explorer.exe" :
  Found: {l:32 b:MYA+B8scqJhGfze+Y7Cx7qMIQdzo1ptjXtIZsBIetQY=} Expected: {l:32 b:1bxQQncXK+XFS2CtXBMgncH3KRMd7whN4+yMcuVMWO8=}
2018-05-22 10:19:12, Info                  CSI    00000390 [SR] Cannot repair member file [l:24{12}]"explorer.exe" of Microsoft-Windows-explorer, Version = 6.1.7601.23537, 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
2018-05-22 10:19:12, Info                  CSI    00000391 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7601.23593_none_6c271b9817e4a753\msi.dll do not match actual file [l:14{7}]"msi.dll" :
  Found: {l:32 b:uPeRhQmdegNjGKJNe0uc49CoISvwDNXtAJ+WlqrZU5c=} Expected: {l:32 b:9zPnwRCsKIuvJd1J13nFCOOuIr+v4s4bM8+w5TavLGE=}
2018-05-22 10:19:12, Info                  CSI    00000392 [SR] Cannot repair member file [l:14{7}]"msi.dll" of Microsoft-Windows-Installer-Engine, Version = 6.1.7601.23593, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2018-05-22 10:19:12, Info                  CSI    00000393 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7601.23537_none_b0517adca98752cc\explorer.exe do not match actual file [l:24{12}]"explorer.exe" :
  Found: {l:32 b:MYA+B8scqJhGfze+Y7Cx7qMIQdzo1ptjXtIZsBIetQY=} Expected: {l:32 b:1bxQQncXK+XFS2CtXBMgncH3KRMd7whN4+yMcuVMWO8=}
2018-05-22 10:19:12, Info                  CSI    00000394 [SR] Cannot repair member file [l:24{12}]"explorer.exe" of Microsoft-Windows-explorer, Version = 6.1.7601.23537, 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
2018-05-22 10:19:12, Info                  CSI    00000395 [SR] This component was referenced by [l:158{79}]"Package_40_for_KB3184143~31bf3856ad364e35~amd64~~6.1.1.4.3184143-41_neutral_LDR"
2018-05-22 10:19:12, Info                  CSI    00000396 Hashes for file member \??\C:\Windows\explorer.exe do not match actual file [l:24{12}]"explorer.exe" :
  Found: {l:32 b:MYA+B8scqJhGfze+Y7Cx7qMIQdzo1ptjXtIZsBIetQY=} Expected: {l:32 b:1bxQQncXK+XFS2CtXBMgncH3KRMd7whN4+yMcuVMWO8=}
2018-05-22 10:19:12, Info                  CSI    00000397 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-explorer_31bf3856ad364e35_6.1.7601.23537_none_b0517adca98752cc\explorer.exe do not match actual file [l:24{12}]"explorer.exe" :
  Found: {l:32 b:MYA+B8scqJhGfze+Y7Cx7qMIQdzo1ptjXtIZsBIetQY=} Expected: {l:32 b:1bxQQncXK+XFS2CtXBMgncH3KRMd7whN4+yMcuVMWO8=}
2018-05-22 10:19:12, Info                  CSI    00000398 [SR] Could not reproject corrupted file [ml:520{260},l:28{14}]"\??\C:\Windows"\[l:24{12}]"explorer.exe"; source file in store is also corrupted
2018-05-22 10:19:12, Info                  CSI    00000399 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7601.23593_none_6c271b9817e4a753\msi.dll do not match actual file [l:14{7}]"msi.dll" :
  Found: {l:32 b:uPeRhQmdegNjGKJNe0uc49CoISvwDNXtAJ+WlqrZU5c=} Expected: {l:32 b:9zPnwRCsKIuvJd1J13nFCOOuIr+v4s4bM8+w5TavLGE=}
2018-05-22 10:19:12, Info                  CSI    0000039a [SR] Cannot repair member file [l:14{7}]"msi.dll" of Microsoft-Windows-Installer-Engine, Version = 6.1.7601.23593, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2018-05-22 10:19:12, Info                  CSI    0000039b [SR] This component was referenced by [l:162{81}]"Package_162_for_KB4048957~31bf3856ad364e35~amd64~~6.1.1.2.4048957-493_neutral_LDR"
2018-05-22 10:19:12, Info                  CSI    0000039c [SR] This component was referenced by [l:164{82}]"Package_500_for_KB4048957~31bf3856ad364e35~amd64~~6.1.1.2.4048957-1917_neutral_LDR"
2018-05-22 10:19:12, Info                  CSI    0000039d Hashes for file member \??\C:\Windows\SysWOW64\msi.dll do not match actual file [l:14{7}]"msi.dll" :
  Found: {l:32 b:uPeRhQmdegNjGKJNe0uc49CoISvwDNXtAJ+WlqrZU5c=} Expected: {l:32 b:9zPnwRCsKIuvJd1J13nFCOOuIr+v4s4bM8+w5TavLGE=}
2018-05-22 10:19:12, Info                  CSI    0000039e Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7601.23593_none_6c271b9817e4a753\msi.dll do not match actual file [l:14{7}]"msi.dll" :

Edited by SophieMayk, 22 May 2018 - 07:11 AM.

  • 0

Advertisements


#2
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,278 posts
Too many bad sectors is not a good sign lets first make sure HDD is working correctly.

Please download and run SeaTools for Windows.

Before the installation begins you will be prompted to either Decline or Accept the terms of the installation, click on I Accept.



1. Once the installation begins SeaTools for Windows will search for HDDs and SSDs on your computer.

2. Detected Drives will list the HDDs and SSDs found. Place a check mark in the drive box you want to run the scan on. This should be the drive that has the operating system installed on it, this is usually C: drive.

3. You will see Basic Tests toolbar above Detected Drives, move the mouse pointer over this to open the test options. Please click on Long Generic Test

4. This will start the scan. When the scan is complete you will see the result under Test Status , please post the results in your topic.

5. The test will indicate either Pass or Fail. Post the results of the scan in your topic.

6. Click on Help, then click on View Log File. If the scan failed take a screen shot of the Log File and post it in your topic.
  • 0

#3
SophieMayk

SophieMayk

    Member

  • Topic Starter
  • Member
  • PipPip
  • 82 posts

Thank you for your response.

 

I ran the test for about 20 minutes and it just sat at 0%, now there's no percentage at all.

 

I'm guessing that is just a bad sign in itself..

 

I ran a Short Generic test and that passed but when I try the long test it just sort of, hangs up?


Edited by SophieMayk, 25 May 2018 - 07:01 AM.

  • 0

#4
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,278 posts
That is a bad sign, if you can leave it running for a few hours.

Can you please tell me brand name of your hard disk drive?
  • 0

#5
SophieMayk

SophieMayk

    Member

  • Topic Starter
  • Member
  • PipPip
  • 82 posts

I've had it running so far for 2 hours and 48 minutes and it's still on 0%

 

It's a WD, the model number is WDC WD10EZEX-60ZF5A0.


  • 0

#6
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,278 posts
This does not look good your hard drive could be failing use Data Lifeguard Diagnostic for Windowsdo a EXTENDED TEST - performs a Full Media Scan to detect bad sectors. Test may take several hours to complete depending on the size of the drive.

You can also if EXTENDED TEST wont work or resolve issue, backup data on the drive and do a FULL ERASE - writes zeros to the drive. File system and data will be lost. Doing Full Erase can sometime repair bad sectors or completely make the already failing drive not usable.

Edited by FreeBooter, 01 June 2018 - 06:44 PM.

  • 0

#7
SophieMayk

SophieMayk

    Member

  • Topic Starter
  • Member
  • PipPip
  • 82 posts

This does not look good your hard drive could be failing use Data Lifeguard Diagnostic for Windowsdo a EXTENDED TEST - performs a Full Media Scan to detect bad sectors. Test may take several hours to complete depending on the size of the drive.

 

So sorry for such a delayed reply, new job and moving got in the way of accessing the PC.

 

I've just started running the test and I already see my Event Log just filling up with Bad Block errors as it's scanning. Every 2 seconds it creates a report and in Data Lifeguard on Current Sector it just freezes the numbers and the time goes up then it goes back down again and continues scanning.

 

It did finally complete and after backing up the PC I clicked repair with the response "Unable to repair bad sectors"; going back to the menu it now has "Fail" next to Extended Test.

 

When I try to click Erase it says that the drive is my System drive with my OS and it cannot be Erased.


Edited by SophieMayk, Yesterday, 06:38 AM.

  • 0






Similar Topics


Also tagged with one or more of these keywords: explorer.exe, windows 7, corrupt, update

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP