3
« on: April 13, 2015, 03:43:53 pm »
More results:
• Yep, Cryptsvc is back and running!
• Pre-scan (run this time in Normal Mode, not Fail Safe) found again tons of files in Windows\servicing\packages with corrupt signature.
- Registering the report into a text file takes ages…
- I converted both the initial and second pre-scan reports into Word and compared them:
The prescan done after the repair job is nearly identical to the initial one. At one place it has just 21 more files indicated as having a corrupt signature.
- The initial run said it had 5786 files handled.
The second run says 5828 files.
- 3 reparse points less in the second run (and still quite some left).
- In total, the Word files containing the reports count over 11000 lines.
I counted 3 lines per error, thus this would mean I have some 3600 corrupted files?
Can a system still run with all that?
- After successful installation of those updates, I ran the pre-scan again. It still shows tons of corrupted files.
• Windows Update is fine again:
- It found 97 new Updates, of which 68 pure Windows updates.
- One of the updates was the System Update Readiness Tool that refused to run before the repair. It installed properly.
- Total time of installation of all the updates was something like 3 hours.
I guess the System Update Readiness Tool has to do with that as well.
• 3rd pre-scan run, after these Windows Updates (run in Normal Mode):
- Shows some 100+ more files with corrupted signature than the prescan done after the repair job…
- This time, it says it handled 6630 files.
- It looks like every single file in there is considered as having a corrupted signature...
Global intermediate conclusion:
• The Windows Repair Tool definitely did some good things, since Windows Update is running OK now and updates do get installed.
• Cold system start up takes more time after than before the repair job (about 2 minutes, which is quite much, given the system specs).
• Another mystery I have not been able to sort out is that after a cold start the network connection icon in the status bar keeps showing a red cross for minutes, way after everything else is up and running. This is something my friend complained about since long and has remained unchanged.
- I did check the repair options for everything that has to do with network but it hasn’t changed anything.
- I notice that the red cross disappears at just about the same moment when an HP alert pops up to tell it can’t find the printer (which is true since the printer is in my friend’s house). I have had serious slowdown problems due to HP software looking every 30 seconds for an absent printer on a laptop. This proved to be because during installation I checked a box stating that I wanted the system to always warn about ink levels…
• The Windows event log only shows 2 minor errors at start up related to HP CueDeviceDiscovery and a missing driver for i8042prt, nothing else. I’m quite sure that the HP CueDeviceDiscovery message has something to do with the afore mentioned delay before networking is established. These messages have been around since long at start up.
• Apart from the long start up and the long time it takes before the network connection is ready (cable connection), the system is perfectly stable.
I will do some more testing tomorrow (it’s over midnight here now).
Thank you anyhow for this great tool.
Even though everything is not sorted out yet, it did its thing!
Show Posts