You have told me previously that you have uploaded it to a file sharing service. Is that correct?
If it is, you should have got a link you could share. Would you mind providing me with a link to the actual files as you are correct, the actual files are indeed too large for them to be uploaded directly.
Unfortunately, it appears that ProcMon has not been run correctly as there is no traces of the error in it.
I did however notice there was a T: drive involved. Is that your system drive? Do you have several system folders spread across multiple drives/partitions?
Could you grab the following file for me in order to analyze it:
<driveletter>\Windows\WinSxS\ManifestCache\548c1bd2e27235ea_blobs.bin or even better copy the whole ManifestCache folder to your Desktop and zip it up for me.
If it is too large, please upload it to OneDrive and provide me with a link.
I have no T: drive. The drives I do have are C: (main), D: (recovery), E: & F: (optical). That's it. In the Run box, this is what I typed:
T\Windows\WinSxS\ManifestCache\548c1bd2e27235ea_blobs.bin
I also tried <T>, No Help. Then I tried T:, No Help. Response all 3 times was Could not find...
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try KB4487078 and if it fails, attach CBS.log.
OK, ran the dotnetfx cleanup tool and restarted my PC. Since I am set to download and install Windows Updates automatically, will Windows Updates start downloading and installing the .net files I am now missing?
Same response...failed to update, Error Code 2. I'll be offline for 12 hours starting now. Microsoft Technical Support, level 3 is contacting me tomorrow to reinstall Windows. Nothing they have done has helped either. I wouldn't be totally surprised that that won't work either, that the problem lies in the KB updates themselves...poorly coded and released.