New
#21
Universal extractor is NOT a good way to extract the required files - it fails to extract a lot of the contained data in msu files properly.
Please post new CheckSUR and SFC scan results.
Universal extractor is NOT a good way to extract the required files - it fails to extract a lot of the contained data in msu files properly.
Please post new CheckSUR and SFC scan results.
I apologize for trying to fix the problem on my own. I was getting desperate and trying all avenues. I cannot work on this computer as much as I would like during the week but that might be better so I don't continue making mistakes! I'll follow your exact instructions moving forward...
I still cannot get the SURT to install so I don't know how to supply you with the checkSUR log file. Can the SURT be run without being installed? I attached the screen shot of my attempt to install SURT a second time. I attached a snip of my files inside the windows log folder. To see if maybe I'm overlooking something or doing something wrong.
What other files are present in the C:\Windows\Logs\CBS folder?
There are no errors at all showing in the CBS.log uploaded.
Here is a snip of the CBS folder and I zipped the newest persist and attached.
Thanks.
Open Event Viewer
click on theWindows logs entry in the left pane to expand it.
Now click on theApplication entry - wait while it loads.
Click on 'File'in the menu bar and select Save...
Save the file asAppevt.evtx
Repeat for theSystem log
then zip both,and upload them.
When I saved the app data it created a folder. I zipped all 3 documents and they are attached.
When I ran windows update earlier I hadn't sent you the new error code yet so do I wanted to update you. I will not take any more action till I hear back from you.
I meant to ask if I should install Symantec again or at least pout some freeware antivirus on the computer while we are trying to fix the problem. I don't want to leave the computer unprotected, but I also don't want to impede our troubleshooting either. Please let me know. We uninstalled it yesterday.
So long as the system is showing genuine, you can install MSE, which will at least tide you over, and is pretty much guaranteed not to interfere with Windows Update.
....still analysing the event logs
Is it my imagination - or has the MSRT stopped installing? (did you Hide it - or is it finally installed/complete?)
The only remaining update is the .NET Framework 4 Client Profile for Windows 7 x64-based Systems (KB982670).
I'm not sure why this is actually being offered at all, since it's been superseded by .NET 4.5 which I thought contained the Client Profile anyway.
This may be the cause of the problem.
I would suggest using Aaron Stebner's tools to check out the .NET installation, and if necessary repair and/or uninstall/reinstall it.
First, go to Microsoft .NET Framework Repair Tool is available and use that - with luck it'll correct what I suspect is a detection error and the demand to install the update will disappear.
If that fails, then the next thing is to rip out .NET 4.x by its roots, and reinstall (be warned - I have known this to fail with the result that it was impossible to reinstall the .NET 4.x, and we had to do a repair install, so it's a bit of a last resort!). You can use this tool for that job...
.NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs