I continues on the path Microsoft kept leading me along and ran Microsoft FixIt
attached is the ResultReport.html it spit out for reference (zipped because it was an html file)
Tried to install updates again and no dice, same errors about not being able to install the service pack
Did you update the chipset driver? My GB MoBo didn't play nice until I did.
I think this guy may be on to something. Follow the instructions present to prep things up for use fo the Readiness Tool. Notice that network issues may still cause it to fail in downloading properly. Try downloading the proper Readiness Tool from your laptop and then transfer it via LAN over to the victim PC and then install it from there.
As for the SDK thing, you can download .NET 4 here
Weird, no new emails came thru saying there were replies.
I have been in the office all week so I didn't have much time.
I did the chipset drivers, very minor improvement, still drops randomly.
Installing .NET right now
So I started to go thru that list...
Downloaded said file: Windows6.1-KB947821-v22-x64.msu
It installed "Hotfix for Windows (KB947821) (update 1 of 1)..."
Checked the CheckSUR.log and it had somethign different than the 3 options listed on the one page:
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 145
Found 3 errors
CBS MUM Corrupt Total count: 2
CBS Catalog Corrupt Total count: 1
Unavailable repair files:
servicing\packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
Different files were listed than the guide, but intuition kicked in and I filled in the blanks...
Found the appropriate 979916 MSU File... Extracted it the files and replaced them.
Reran the Windows6.1-KB947821-v22-x64.msu
Rechecked the CheckSUR.log
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 120
No errors detected
Ran SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
Time to restart and see if I can install the outstanding windows updates that linger and if it fixes my network
OK, so I finally have all of my updates installed - had to do a few manually because Windows Update wasn't cooperating, but I think I am finally there...
Now to determine if my connection is stable (at work right now so I can't do this til tonight)
I thought it was going to be stable but no dice... As you can see in the attachment, it goes full speend then craps out for a bit, full speed, crap... back and forth...
This particular instance was downloading a 300MB+ file... 2-3 meg come down with no issue, anything larger it chokes.
The drops look like they aren't systematic. Can you verify if there's a pattern to them or if it's just randomness in either timing or length?
As for logging all this, your options is to either produce a log from Performance Monitor (startup guide here), Xperf, or ProcMon.
For Xperf, you'll need to have the Windows SDK installed, specifically the "Performance Toolkit" for it. This is a good guide on how to setup and run Xperf properly to log network-based activity. You'll want strict instances where you are solely performing specific operations like just downloading a large file, or playing a game. I believe you do not need to do the heap logging, so you can disregard that portion of the guide. Xperf is probably the most thorough log for us to look at, aside from ProcMon. Unlike ProcMon, however, it's a bit easier to read.
For ProcMon, grab it here, then open it. Immediately stop capturing by clicking the magnifying glass button, then clear entries by clicking the eraser button next to it. Then, start a download of a large file or something. Start capturing by clicking the magnifying button again and let it capture a moment when the network speed plummets. Then save as (make sure to check "all events") a procmon log.
For both Xperf and Procmon logs, I really doubt either will fit here as an attachment, so you may need to use something like MirrorCreator.com or whatever to upload it to some 3rd-party filesharing sites.
Quote