Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Corrupted "vbc.exe" File After Last Win10 Update


  • Please log in to reply
11 replies to this topic

#1 JoLynch

JoLynch

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 02 March 2017 - 08:49 AM

Well, hopefully I've posted this in the right place.

 

I’ve had a series of unfortunate events with my PC, starting with the dreaded “unable to detect disc drive” at startup. This occurred shortly after the last Windows update (KB4010250)/(KB890830). It booted to the BIOS, indicating 0 errors. And so I rebooted as usual. Via the (C:) Properties > Tools tab, I ran the Check option out of suspicion. There was some problems, which it cleaned up. It restarted successfully and is currently running with no problems.

 

I went on to do a sfc /scannow via Command Prompt. Unfortunately, some integrity issues were found, claiming: “Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.”

 

I could not see any errors on the CBS log, at first. The list is pretty grueling. So, I ran C:\WINDOWS\system32>DISM.exe/Online /Cleanup-image /ScanHealth. It said that the component store was repairable, and the operation completed successfully.

 

I then hit C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth, and Error 0x800f081f came up:

 

“The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.”

 

 

I was officially at a loss. After looking at the CBS log once more, I noticed this:

 

 

2017-03-02 04:50:14, Info CSI    0000588c [SR] Cannot repair member file [l:7]'vbc.exe' of NetFx4-vbc_exe, version 4.0.14305.0, arch x86, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, file is missing
2017-03-02 04:50:14, Info CSI    0000588d [SR] This component was referenced by [l:82]'Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~amd64~~10.0.14393.0.NetFx4'
2017-03-02 04:50:14, Info CSI    0000588e [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\vbc.exe; source file in store is also corrupted

2017-03-02 04:50:16, Info CSI 000058da [SR] Cannot repair member file [l:7]'vbc.exe' of NetFx4-vbc_exe, version 4.0.14305.0, arch x86, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, file is missing

2017-03-02 04:50:16, Info CSI 000058db@2017/3/2:12:50:16.522 Primitive installers committed for repair

2017-03-02 04:50:16, Info CSI 000058dc [SR] Cannot repair member file [l:7]'vbc.exe' of NetFx4-vbc_exe, version 4.0.14305.0, arch x86, versionScope neutral, pkt {l:8 b:b03f5f7f11d50a3a} in the store, file is missing

2017-03-02 04:50:16, Info CSI 000058dd [SR] This component was referenced by [l:82]'Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~amd64~~10.0.14393.0.NetFx4'

2017-03-02 04:50:16, Info CSI 000058de [SR] Could not reproject corrupted file \??\C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\vbc.exe; source file in store is also corrupted

 

 

So it seems that this “vbc.exe” is the culprit. There's a number of these errors mentioned throughout the log. I have no idea how to type this out in Command Prompt, in regards to specifying the DISM.exe source. (Or if I should even attempt to, in the first place.) I understand that this is a process that belongs to either Microsoft Visual Studio, or the .NET Framework.

 

As to how this file got “corrupted”... A virus seems unlikely, as I have an active anti-virus (Webroot), and also run Malwarebytes for a weekly additional scan. Nothing malicious has come up. Only thing I can think of is, this last Windows 10 update may have borked something. (I should mention that I additionally ran the CHKDSK command, and did a number of separate hard drive diagnostic tests. Everything came out fine, so a hard drive malfunction also seems unlikely.)

 

Would anyone have any ideas how to proceed with this via Command Prompt using the DISM.exe line? And what I should be inputting? I am not exactly tech-savvy about all this stuff.  

 

Thanks a bunch,

-J.


Edited by JoLynch, 02 March 2017 - 10:49 AM.


BC AdBot (Login to Remove)

 


#2 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:24 AM

Posted 03 March 2017 - 11:40 AM

Hi

 

Could you run sfc /scannow again? Once you do, attach the C:\Windows\Logs\CBS\CBS.log in your next reply. From there, I will try to source the files

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#3 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 03 March 2017 - 05:15 PM

Hiya,

 

Thanks for the response. The CBS log has been attached. (And apologizes in advance - it's painfully long.) Let me know if there's any attachment issues.

 

Cheers,

-J.


Edited by JoLynch, 03 March 2017 - 05:21 PM.


#4 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 03 March 2017 - 05:23 PM

Hmm. It looks like the file is not attaching properly. (Or if it did, I cannot see it.) Tried a couple times. Is there another way to attach logs, other than through the More Reply Options > Add Attachment tab? The file should be uploading - it's not that large. I could always copy + paste, but that'd be a wall-of-text-syndrome post nightmare.


Edited by JoLynch, 03 March 2017 - 05:27 PM.


#5 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:24 AM

Posted 04 March 2017 - 11:44 AM

Hi

 

Since the attachment is not working, I suggest that you use a service like OneDrive or Google Drive and post the share link for the file here. Thanks

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#6 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 06 March 2017 - 10:47 PM

Duly noted. The file has been uploaded here. Let me know if there are any issues.

 

Thanks again,

-J.



#7 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:24 AM

Posted 07 March 2017 - 09:53 AM

Hi

 

Download SFCFix.exe (by niemiro) and move the executable on your Desktop. Then, run it and it will create the SFCFix.txt log on the Desktop. Copy and paste the log in your next reply :)

 

Thanks,

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#8 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 07 March 2017 - 08:40 PM

Hello again,

 

Ran SFCFIX.exe, and... it found nothing. (I did temporarily disable my anti-virus during the scan, as a side note. Not entirely sure if it was necessary.)

 

 

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-03-07 16:45:38.375
Microsoft Windows 10 Build 14393 - amd64
Not using a script file.
 
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
 
Successfully processed all directives.
 
Failed to generate a complete zip file. Upload aborted.
 
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-03-07 16:56:55.702
----------------------EOF-----------------------
 
 
I did run DISM.exe /Online /Cleanup-image /Restorehealth after another sfc/ scannow, shortly afterwards. It claimed that the damaged files could not be corrected... again. I saved the DISM log from that last scan, if you'd think that'd help any. (Or is this a type of log that has security credentials/info that should not be shared online? I honestly have no idea what I am looking at.) Otherwise, I noticed that the current CBS log shows a corrupt CSI Payload:
 
Checking System Update Readiness.
 
(p) CSI Payload Corrupt x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73\vbc.exe
Repair failed: Missing replacement payload.
 
Summary:
Operation: Detect and Repair 
Operation result: 0x800f081f
Last Successful Step: Entire operation completes.
Total Detected Corruption: 1
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 1
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
 
Total Operation Time: 587 seconds.
 
2017-03-07 17:20:28, Info                  CBS    CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB]
2017-03-07 17:20:28, Info                  CBS    Count of times corruption detected: 1
2017-03-07 17:20:28, Info                  CBS    Seconds between initial corruption detections: -1
2017-03-07 17:20:28, Info                  CBS    Seconds between corruption and repair: -1
2017-03-07 17:20:28, Info                  CBS    SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2017-03-07 17:20:28, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-03-07 17:20:28, Info                  CBS    Reboot mark cleared
2017-03-07 17:20:28, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2017-03-07 17:20:28, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-03-07 17:20:28, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30578600_3450856059 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-03-07 17:20:28, Error                 CBS    Session: 30578600_3450856059 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-03-07 17:20:28, Info                  CBS    Session: 30578600_3450856059 finalized. Download error: 0x800f0948 [CBS_E_SOURCE_MISSING_FROM_WU_CAB], Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2017-03-07 17:20:28, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
2017-03-07 17:22:28, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2017-03-07 17:22:28, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-03-07 17:22:28, Info                  CBS    Ending the TiWorker main loop.
2017-03-07 17:22:28, Info                  CBS    Starting TiWorker finalization.
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: WcpUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: DrupUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: DpxUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: SrUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2017-03-07 17:22:28, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2017-03-07 17:22:28, Info                  CBS    Ending TiWorker finalization.
2017-03-07 17:22:28, Info                  CBS    Ending the TrustedInstaller main loop.
2017-03-07 17:22:28, Info                  CBS    Starting TrustedInstaller finalization.
2017-03-07 17:22:28, Info                  CBS    Winlogon: Stopping notify server
2017-03-07 17:22:28, Info                  CBS    Winlogon: Unloading SysNotify DLL
2017-03-07 17:22:28, Info                  CBS    Ending TrustedInstaller finalization.
 
Push comes to shove, if we're unable to figure out which file is damaged, would it be a good idea to do a system restore? Hopefully, it won't come to that, but...  :mellow:
 
Cheers,
-J.

Edited by JoLynch, 07 March 2017 - 11:04 PM.


#9 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:24 AM

Posted 12 March 2017 - 12:43 PM

Hi

 

Could you run this fix?:

 

SFCFix Fix
This fix is very specific for JoLynch's computer. Trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.
 
Download SFCFix.exe (by niemiro) and move the executable on your Desktop.
Download SFCFix.zip from here and move the archive to your Desktop
Note: Make sure that the file is named SFCFix.zip, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix.zip file over the SFCFix.exe executable and release it

mMabJGT.gif

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
 
Run sfc /scannow again just to make sure. If it still finds corrupt files, attach the C:\Windows\Logs\CBS\CBS.log again.
 
-CKing

If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#10 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 14 March 2017 - 08:07 AM

Followed your instructions; still unable to fix the file through both SFCFIX.exe and SFC /scannow. Here's the log result: 

 

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-03-14 05:36:46.052
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\JoLynch\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73

Failed to copy file C:\Users\JoLynch\AppData\Local\niemiro\Archive\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73\vbc.exe to C:\WINDOWS\WinSxS\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73\vbc.exe with error code ERROR_ACCESS_DENIED.

Successfully restored ownership for C:\WINDOWS\WinSxS\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73
PowerCopy:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-03-14 05:36:46.692
Script hash: UVhUIIMfHE4WqAZjAvXMbV7o04ssk+zYw4bLMuq6Eco=
----------------------EOF-----------------------

 

I've uploaded the latest CBS log to here. Still haven't the foggiest what this file is used for. If it's a super important core file, maybe a system restore is inevitable. (At least presently, PC is running fine. No strange glitches... yet).

 

Let me know what you think,

-J.


Edited by JoLynch, 14 March 2017 - 08:46 AM.


#11 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:08:24 AM

Posted 14 March 2017 - 11:49 AM

SFCFix failed to copy it:

Failed to copy file C:\Users\JoLynch\AppData\Local\niemiro\Archive\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73\vbc.exe to C:\WINDOWS\WinSxS\x86_netfx4-vbc_exe_b03f5f7f11d50a3a_4.0.14305.0_none_ebe84c1b0e7ebf73\vbc.exe with error code ERROR_ACCESS_DENIED.

Could you run this fix instead? This should hopefully repair the issue:

 

 

SFCFix Fix
This fix is very specific for JoLynch's computer. Trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.
 
If you already have SFCFix.exe, use that instead. If you don't, download SFCFix.exe (by niemiro) and move the executable on your Desktop.
Download SFCFix.zip from here and move the archive to your Desktop
Note: Make sure that the file is named SFCFix.zip, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix.zip file over the SFCFix.exe executable and release it

mMabJGT.gif

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
 
Run sfc /scannow again and attach the CBS.log if it finds corrupt files
 
-CKing

If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase


#12 JoLynch

JoLynch
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:24 AM

Posted 14 March 2017 - 12:01 PM

 

SFCFix Fix
This fix is very specific for JoLynch's computer. Trying this fix on your own computer might damage your computer. If you are after assistance, create a new thread, and you will be assisted shortly.
 
If you already have SFCFix.exe, use that instead. If you don't, download SFCFix.exe (by niemiro) and move the executable on your Desktop.
Download SFCFix.zip from here and move the archive to your Desktop
Note: Make sure that the file is named SFCFix.zip, do not rename it.
Save any work you have open, and close every programs
Drag the SFCFix.zip file over the SFCFix.exe executable and release it

mMabJGT.gif

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
 
Run sfc /scannow again and attach the CBS.log if it finds corrupt files
 
-CKing

 

 

Hello Again,

 

I did in fact do all this, which is what the previous post is showing (the current CBS log link is available there, too.) I went ahead and did it again, but it's just showing the exact same results:

 

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-03-14 09:55:55.739
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\JoLynch\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319

Failed to copy file C:\Users\JoLynch\AppData\Local\niemiro\Archive\Microsoft.NET\Framework\v4.0.30319\vbc.exe to C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\vbc.exe with error code ERROR_ACCESS_DENIED.

Successfully restored ownership for C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
Successfully restored permissions on C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
PowerCopy:: directive failed to complete successfully.

RepairPermissions:: directive completed successfully.

Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-03-14 09:55:56.161
Script hash: JGY0XjO6jAuQtockzjHLB6kqocbQDV+Rv62pV+BHBlg=
----------------------EOF-----------------------

 

Looks like this file cannot be repaired. Still not entirely sure what this is, but I think this may be an older .NET Framework update, or some other outdated file. This isn't exactly considered mandatory, is it? (As a side note, I tried reinstalling the latest Framework update; Windows claims that it's up-to-date and working properly). 

 

Cheers,

-J.


Edited by JoLynch, 14 March 2017 - 01:56 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users