Solved Won't restore system after driver updates broke cherrytree & ccleaner

[treehouse]

Won't restore system after driver updates broke cherrytree & ccleaner

I'm wondering whether to try advanced methods of restoring my laptop to an earlier time. Normal method reports success, but doesn't fix problem and shows same restore points next time. I was about to try from Safe Mode, but thought I'd drop in here first (no undo).

Short description of issue
After updating drivers (reported in DriverEasy) - Intel Management Interface, Realtek High Definition Audio, Realtek PCIe FE Family Controller and Intel HD Graphics - I found that Cherrytree (editor) window wouldn't display. It is normally hidden with an icon in the notification area, showing when clicked. It now shows very briefly, then disappears again, although showing its item in the taskbar. I've also noticed (after various attempts to restore system) that Ccleaner won't run, giving the error that I don't have permission, and its icon has changed, maybe to the default for unrecognised exes.

I had made restore points, so when I noticed the problem with cherrytree, I decided to use the restore points to go back one at a time until it was fixed, but discovered that it wasn't going back.

More details
However, the process was complicated by the fact that I had tried to get around the slow download speed of the manual version of Driver Easy by searching online for the Realtek PCIe FE Family Controller driver to download and install manually, making sure it was the same version, 7.112.0811.2017. I intended to continue this way for any further driver installation. However, I happened to find this version at the website of DriverMax, and I made the mistake of ticking the box to "scan for other outdated drivers". DriverMax automatically installed the driver and, of course, DriverMax itself.

At first, I was impressed with DriverMax, it looked like it would let me install drivers more easily, so (IIRC), I tested it by doing the first on its list from within its UI, the Intel HD Graphics. I think this was when I noticed the cherrytree error, because I make notes there of such things, and I also used the in-built Restore feature of DriverMax to try to reverse this (it allows you to choose a restore point and instigates the System Restore), which was when I found that it wasn't going back.

I reverted to using System Restore directly, which also didn't go back (but each time reported success). I tried various earlier points (I haven't tried the latest system-generated one yet), to no avail. I was by now suspicious of DriverMax, which doesn't even have an option not to run at startup, and thought that might be interfering, so uninstalled it. Same. I researched and found advice that antivirus can interfere with Restore, so I suspended services on Avast until after restart. Same.

I thought perhaps the cherrytree issue was not directly related, or could be fixed independently, so reinstalled the latest version again. Same.

I ran Avast smart scan in case of infection. None found. I thought I'd check Ccleaner for its list of restore points, etc., and was denied access, then noticed its icon was wrong.

Do you advise trying a restore point via safe mode, or via installation disc utilities, or something else?

Prior to starting this, I backed up files to an external drive, so data should be safe. I don't have a disc image, and I didn't make a rescue disc. I do have the Windows7 installation disc.

 

[torchwood]

Hi Treehouse,

NOT a fan of 3rd party driver updaters, MS does a pretty good job
OEM drivers are favourite from your homepage
Custom Build ALLWAYS from the manufacturers site.

Something has obviously corrupted System restore, Safe mode will still only find the same restore points.
There is a LAST known good option, you could try that.

As you have all your files backed up externally, might be worth your while doing a clean install, updating everything apart from Cherrytree, NOW create a system image
Imaging with free Macrium - Windows 7 Help Forums

Now start playing with Cherrytree, image re-install 10-15 mins if it ruins your system
once installed and NO probles create new image


Roy

 

[torchwood]

Just looked at your specs

2GB with W7 is NOT really enough for a 64bit install- min 3GB.

Roy

EDIT

My mrs has the same lappy- it came with 3GB?? somebody taken some out????
just read your previous thread
YOUR backup W7 key is on the COA sticker
i can provide a W7 Iso
can you also copy/paste the results from this tool i want to check something
http://go.microsoft.com/fwlink/?LinkID=52012

i DO NOT believe the install is non-genuine

 

[treehouse]

Hi Torchwood, great info, thanks.

NOT a fan of 3rd party driver updaters

Me neither now! I'll use MS from now on. Lesson learned.

There is a LAST known good option, you could try that.

OK. Thanks.

As you have all your files backed up externally, might be worth your while doing a clean install

Really rather not, but I guess it's a possible option. One issue is that MS gave me a "one-time" activation key, and I don't want to get into all that wrangle again if it won't recognise it. In fact, I just won't. I'll install Linux.

Just looked at your specs

2GB with W7 is NOT really enough for a 64bit install- min 3GB.

Roy

EDIT

My mrs has the same lappy- it came with 3GB?? somebody taken some out????

Nah. It'll have had Vista on originally. Seems pretty good, actually, but I know it's not enough. I just haven't got around to putting another 2 GB in yet. Had to get a new hard-drive after that crash and went SSD, which seems to help, but I'm not doing much that needs loads of memory.

just read your previous thread
YOUR backup W7 key is on the COA sticker
i can provide a W7 Iso

All sorted now, thanks.

can you also copy/paste the results from this tool i want to check something
http://go.microsoft.com/fwlink/?LinkID=52012

i DO NOT believe the install is non-genuine

Could you just tell me a bit more about it first or where I can read about it? I don't want to just install something at this stage without knowing why. What is it you're wanting to check? I'm pretty sure the ISO I burned is legit.

 

[torchwood]

Hi Treehouse,

the tool
Its purely a diagnostic report about how your system has been activated and registered with MS, and has been posted in multiple forums including MS, thousands of em.
There is NO personal data in it.

It will show a partial product key last 3 sets only
(belarc will show the complete key DONT post it.)

im more interested in what type of licence,
then i can provide a link for a W7 service pack 1 Iso download, from MS servers

I do find it odd that comp came with Vista, as i said my mrs has got one, the COA sticker will also show the originally installed OS

As youve only got 2GB the Iso can be for a 32bit option the key should be valid for both


As it sounds like you dont want to go the clean install route the Iso can be used to perform a repair install NO LOSS of personal data but it will repair corrupted registry entries
Repair Install - Windows 7 Help Forums


Roy

 

[treehouse]

Cheers Buddy...
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-Q69TJ-G3YBJ-KW8XW
Windows Product Key Hash: cQJO3zIxtDOCeiJ5+AhFZ+JYlRM=
Windows Product ID: 00359-114-4402047-85599
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {60B857E6-E192-4AB7-B579-3049235DA3A7}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_ldr.170810-1615
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{60B857E6-E192-4AB7-B579-3049235DA3A7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-KW8XW</PKey><PID>00359-114-4402047-85599</PID><PIDType>5</PIDType><SID>S-1-5-21-2785788139-3172466215-127188836</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite C660</Model></SYSTEM><BIOS><Manufacturer>TOSHIBA</Manufacturer><Version>2.00</Version><SMBIOSVersion major="2" minor="6"/><Date>20120509000000.000000+000</Date></BIOS><HWID>C9333107018400FC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSCPL</OEMID><OEMTableID>TOSCPL00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: 2e7d060d-4714-40f2-9896-1e4f15b612ad
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00170-114-440204-00-2057-7601.0000-1042017
Installation ID: 003404301293133095243375855323079553786884875845513441
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: KW8XW
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 23/09/2017 23:29:19

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 7:24:2017 10:52
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: LgAAAAEAAgABAAEAAAABAAAAAgABAAEAJJSAHxKJpF+aUcgvemICWxivWERcXQ==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC TOSCPL TOSCPL00
FACP TOSCPL TOSCPL00
HPET TOSCPL TOSCPL00
MCFG TOSCPL TOSCPL00
ASF! TOSCPL TOSCPL00
SLIC TOSCPL TOSCPL00
SSDT PmRef CpuPm
UEFI PTL PTLBUF8
UEFI PTL PTLBUF8
UEFI PTL PTLBUF8

 

[torchwood]

Hi treehouse,

Jolly decent of MS to give you a Retail key, it can be transferred to ANY computer.

Looking at that report it looks like the original OS was 7 not Vista

anyway
you can try either the clean or repair install with this D/l
W7 SP1 X64 home premium

https://software-download.microsoft...1506294353&h=72847bc7534f643b67031a8ae8103fad


This link is only valid till midnight Sunday.

DONT FORGET TO PULL THE FULL KEY using Belarc you WILL need it
Belarc - System Management For The Internet Age. Software license management, IT asset management, IT security, Cyber Security.



Roy

 

[torchwood]

Hi Treehouse,,

Are you running UEFI bios, it didnt come with that, doesnt matter unless your planning to clean install


Roy

 

[treehouse]

Hi Roy, I don't understand the need for this download. Can't I just use the disc I burned already when I did the last full reinstall?

Also, when you say "repair install", is that the same as using rescue utilities, either from the extended boot menu or the installation disc?

This is all well above my pay grade. You seem to have come to the conclusion that some kind of reinstall is required. Are you sure it's not possible to diagnose the problem and do something less drastic to fix it?

You suggested the last known good option, but when I select that, the additional info says that it will use the settings from the last known successful boot. I'm not sure that's much use, since it's booting fine.

Edit: I don't know if it's UEFI, but I don't think so.

Thanks for your help,
John

 

[SIW2]

This is what he meant

Repair Install - Windows 7 Help Forums

 

[treehouse]

This is what he meant

Repair Install - Windows 7 Help Forums

Thanks SIW2 - lots to read there if I decide to try a repair install. It's a lot to get my head round and I need to check I know which category my system is in.

I'm still hoping something else might fix it without that.

I just realised today, I've not actually tried manually rolling back the drivers I updated - should I try that, do you (anyone) think? If it's just that I've installed a driver that's wrong somehow, theoretically that should fix it if it will roll back. If it's some other glitch has corrupted something, it might not. I know I seem very cautious - just thought someone might say "NOOOOO! Don't do that!" Lack of caution got me into this mess.

Edit to add: Also, if doing a System Restore to an earlier point from Safe Mode doesn't have an undo option, this suggests that it's different from the normal mode. Would you advise this? As I said, the problem was that System Restore was reporting success, but failing to actually go back to an earlier restore point. Perhaps from Safe Mode there's some reason it might succeed?

 

[torchwood]

Hi Treehouse,

Its allways better to get it from the horses mouth.
the download link is directly from MS servers, and there's no bloatware, just the OS.

The MAJOR plus about a repair install is that it ONLY plays with the MS part of your system.
IT leaves YOUR personal files alone.

You can allways roll-back drivers if the option is available. its a common proceedure
Your problem was and is the loss of your System Restore options, the repair install will fix-it
I dont believe this was caused by a driver.

You coud try a couple of other fix-its
KB947821, known as SURT, could take a while to run
and from an elevated command mode
sfc /scannow.

I can ony give you advise its up to you which way you go.

Roy

 

[treehouse]

Hi Treehouse,

Its allways better to get it from the horses mouth.
the download link is directly from MS servers, and there's no bloatware, just the OS.

Sure, I know the ISO doesn't have bloatware. I mean the bloatware from Toshiba. If the repair install (or, obviously, the full install) removed the Toshiba drivers, I'd have to go back and install them again, and it took a long time before researching which were necessary and which were garbage, that's all. But you say...

The MAJOR plus about a repair install is that it ONLY plays with the MS part of your system.
IT leaves YOUR personal files alone.

So that might help.

You can allways roll-back drivers if the option is available. its a common proceedure
Your problem was and is the loss of your System Restore options, the repair install will fix-it
I dont believe this was caused by a driver.

I would guess it was either a driver or the installation/operation of DriverMax, as that's all I did. It's possible that using DriverMax to instigate a restore might have broken System Restore, but I only did that because cherrytree wouldn't open, so some kind of issue was already present, at least.

One thought was that maybe an incorrect driver might cause System Restore to fail - are you suggesting that is impossible or unlikely? Never mind, I might just see if I can roll them back and find out. I probably need to start taking steps of some kind.

You coud try a couple of other fix-its
KB947821, known as SURT, could take a while to run

Thanks. I'll read up on it.

and from an elevated command mode
sfc /scannow.

Interesting. I was reading about that and almost asked about it too. It's very confusing for a non-nerd, all the different options for trying to recover a working system!

I can ony give you advise its up to you which way you go.

I appreciate your advice very much indeed. Please don't take my asking questions as criticising your advice. They're just because you're way ahead of me and I want to fill the gaps a bit.

If I could trouble you again, is there some advantage to using a new download of a Windows 7 installation/repair disc over the one I used to install the current version? I told MS where I got it and they confirmed that it was the correct thing, so I already have a working disc. Windows has been working fine until I broke it, presumably by using proprietary driver update software.

 

[treehouse]

I've had a look at the four device drivers I updated, and I'm even more confused. I suspect that at least one of them either didn't update or did roll back with a System Restore, as far as I can remember from the driver dates, IDs, etc., so I'm not going down that route.

I think I'll try sfc /scannow
Fingers crossed.icnic:

 

[treehouse]

Ran OK, found no integrity violations.

 

[torchwood]

Hi John,

No Worries, (unless your a Man U fan - up the Saints)

I supplied the link as its the latest available, includes Service pack 1, not sure how old yours is.

Unfortunately the system can be corrupted, by 3rd party software or more often Windows Updates.
quite often the problem usually doesnt show itself immediately

Little tip for a clean install OEM computer, they often have a system updater yours is Service Centre, run once then uninstall, windows Update will then take over.

dont forget to run Kb947821, it repairs more data than sfc.

Roy

 

[treehouse]

Hi torchwood,

No Worries, (unless your a Man U fan - up the Saints)

Not a football fan at all, so definitely, up the Saints - it's all the same to me!

I supplied the link as its the latest available, includes Service pack 1, not sure how old yours is.

Good point. I have SP1, but I'm not sure the disc was, or if it got updated since. Probably the latter.

Little tip for a clean install OEM computer, they often have a system updater yours is Service Centre, run once then uninstall, windows Update will then take over.

Sorry, could you unpack that a bit for noobs? I've no idea what it means!

dont forget to run Kb947821, it repairs more data than sfc.

Nifty - here's the summary (would the full log help, I didn't want to post it in case there's a security issue or anything?)

Summary:
Seconds executed: 457
 Found 101 errors
 Fixed 89 errors
  CSI Unexpected Failure Total count: 6
  CSI F Mark Bad Type Total count: 89
  Fixed: CSI F Mark Bad Type.  Total count: 89
  CSI Missing Winning Component Key Total count: 6

I wonder if I can find fixes for the other 12.
There's no obvious difference with the two visible issues - cherrytree still not showing (actually, I just realised it's only not showing when normal, it'll maximize, but the behaviour is messed up - at least I can make some notes again!) and Windows still can't access ccleaner. But fixing 101 89 errors is a good start.

I haven't tried seeing if System Restore works. The problem is that I don't want to go back now and undo any improvements this has made. I guess I could create two restore points and see if it'll wind back to the first one.

 

[torchwood]

Hi John,

Good news/Bad news

it actually fixed 89

Those other 12 CSI errors UUUUURGH.
especially the 6 unexpected failures type -
Never seen that before so no way i can fix them

Wouldn't mind seeing them, there are no security/other issues in them, can you post the log.

as i said in post #2, create an image, reinstall time 15min
Imaging with free Macrium - Windows 7 Help Forums
Then try a system restore.

The little OEM tip.
Go to the driver homepage for your lappy. one of the options will be either Utilities or possibly Service Centre. download/install/run - It will check your comp for out of date versions and give you the option
to install or NOT.

Roy

 

[treehouse]

Cheers Roy,

I'll look into Macrium etc. ASAP, thanks.
I think maybe you overestimated my prior knowledge when you said,

As you have all your files backed up externally, might be worth your while doing a clean install, updating everything apart from Cherrytree, NOW create a system image.
Now start playing with Cherrytree, image re-install 10-15 mins if it ruins your system
once installed and NO probles create new image

Also, I was unsure how you were using the word "NOW" - i.e. "THEN"? or "RIGHT NOW"? It's all a bit terse. I'm sure it would make sense if I already knew what you're talking about.

Couple of other things:

1. There's no point making an image while things are broken, is there? The whole partition is re-written when restoring it, yes? What is the point in doing that until things are fixed? If it comes to re-installing Windows and I'm about to do further stuff, installing drivers, etc., Sys Restore would be fixed, so shouldn't I be able to just use that? I backup files, but didn't do an image, I think because the drive I use didn't have enough space. I guess I'll need to buy another drive or make space somewhere.

2. Is there some reason you're suggesting using Macrium rather than the built-in Windows image-writing routine (I presume that's what it is, within the usual Backup feature)?

The little OEM tip.
Go to the driver homepage for your lappy. one of the options will be either Utilities or possibly Service Centre. download/install/run - It will check your comp for out of date versions and give you the option
to install or NOT.

Out of date versions of what? Toshiba Drivers?

I feel bad I'm taking so much of your time, and I appreciate your help a lot. I hope you're getting something out of it!

Full report from SURT follows in next post.

 

[treehouse]

Here you go...it's still too long for one post, so I'll split it!...

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-09-25 18:56

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI F Mark Bad Type    0x000000DE    f!mfc140u.dll     x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb\f!mfc140u.dll:  mfc140u.dll
(f)    CSI Missing Winning Component Key    0x00000000     x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb         
(f)    CSI Unexpected Failure    0x00000005    14.0.24210.0     x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb     Error deleting winners map value.
(f)    CSI Missing Winning Component Key    0x00000000     amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc         
(f)    CSI Unexpected Failure    0x00000005    14.0.24210.0     amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc     Error deleting winners map value.
(f)    CSI Missing Winning Component Key    0x00000000     x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702         
(f)    CSI Unexpected Failure    0x00000005    14.0.24210.0     x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702     Error deleting winners map value.
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-heap-l1-1-_489a8453031dbf7e     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-heap-l1-1-_489a8453031dbf7e:  api-ms-win-crt-heap-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!msvcp140.dll     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!msvcp140.dll:  msvcp140.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-runtime-l1_295c38be07a80c5c     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-runtime-l1_295c38be07a80c5c:  api-ms-win-crt-runtime-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-util-l1-1_2fbbddc80bd7b142     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-util-l1-1_2fbbddc80bd7b142:  api-ms-win-core-util-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-time-l1-1-_0a06182b126e5ced     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-time-l1-1-_0a06182b126e5ced:  api-ms-win-crt-time-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-filesystem_4c8d668a165bcfc5     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-filesystem_4c8d668a165bcfc5:  api-ms-win-crt-filesystem-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-rtlsuppor_957ea04417ffd3fd     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-rtlsuppor_957ea04417ffd3fd:  api-ms-win-core-rtlsupport-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-processth_be90e7a218743905     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-processth_be90e7a218743905:  api-ms-win-core-processthreads-l1-1-1.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-processth_bcaa70081b4dec6c     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-processth_bcaa70081b4dec6c:  api-ms-win-core-processthreads-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-synch-l1-_58d5510126a3d0a3     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-synch-l1-_58d5510126a3d0a3:  api-ms-win-core-synch-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-synch-l1-_58b1482526f4e492     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-synch-l1-_58b1482526f4e492:  api-ms-win-core-synch-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-stdio-l1-1_91720ce12a362805     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-stdio-l1-1_91720ce12a362805:  api-ms-win-crt-stdio-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-string-l1-_bf364c6133dc5f29     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-string-l1-_bf364c6133dc5f29:  api-ms-win-crt-string-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!vcruntime140.dll     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!vcruntime140.dll:  vcruntime140.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-timezone-_36a3847554301d1b     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-timezone-_36a3847554301d1b:  api-ms-win-core-timezone-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-errorhand_74d332585a874f13     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-errorhand_74d332585a874f13:  api-ms-win-core-errorhandling-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-utility-l1_ee0406a3668937c8     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-utility-l1_ee0406a3668937c8:  api-ms-win-crt-utility-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-debug-l1-_fcf709b567764adb     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-debug-l1-_fcf709b567764adb:  api-ms-win-core-debug-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-convert-l1_ccd6145476992bb5     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-convert-l1_ccd6145476992bb5:  api-ms-win-crt-convert-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-interlock_5b13ca157c86206a     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-interlock_5b13ca157c86206a:  api-ms-win-core-interlocked-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-locale-l1-_78d5406182e89c10     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-locale-l1-_78d5406182e89c10:  api-ms-win-crt-locale-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-memory-l1_b50269be86981cdf     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-memory-l1_b50269be86981cdf:  api-ms-win-core-memory-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-file-l2-1_55576bbe8d24bad1     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-file-l2-1_55576bbe8d24bad1:  api-ms-win-core-file-l2-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-file-l1-2_5641c4568eb992f3     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-file-l1-2_5641c4568eb992f3:  api-ms-win-core-file-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-file-l1-1_545b4cbc9193465a     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-file-l1-1_545b4cbc9193465a:  api-ms-win-core-file-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-environmen_51aa2ca79964c47b     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-environmen_51aa2ca79964c47b:  api-ms-win-crt-environment-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!ucrtbase.dll     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!ucrtbase.dll:  ucrtbase.dll
(f)    CSI F Mark Bad Type    0x000000DE    f!concrt140.dll     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!concrt140.dll:  concrt140.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-datetime-_18c69a37b29c8a6b     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-datetime-_18c69a37b29c8a6b:  api-ms-win-core-datetime-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-string-l1_01a67a1eb4a37927     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-string-l1_01a67a1eb4a37927:  api-ms-win-core-string-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-heap-l1-1_287b5c03b6af9938     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-heap-l1-1_287b5c03b6af9938:  api-ms-win-core-heap-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-processen_53b32beeba773f3c     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-processen_53b32beeba773f3c:  api-ms-win-core-processenvironment-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-profile-l_589cdc13bb19940f     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-profile-l_589cdc13bb19940f:  api-ms-win-core-profile-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-math-l1-1-_a0c2a56cbb4edb5a     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-math-l1-1-_a0c2a56cbb4edb5a:  api-ms-win-crt-math-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-console-l_47586507cb37b721     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-console-l_47586507cb37b721:  api-ms-win-core-console-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-process-l1_97bd49b0cc348583     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-process-l1_97bd49b0cc348583:  api-ms-win-crt-process-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-multibyte-_73a631bfd5b88d97     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-multibyte-_73a631bfd5b88d97:  api-ms-win-crt-multibyte-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-localizat_2f8df132e6bb3940     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-localizat_2f8df132e6bb3940:  api-ms-win-core-localization-l1-2-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-crt-conio-l1-1_802b0af5ede3c7ee     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-crt-conio-l1-1_802b0af5ede3c7ee:  api-ms-win-crt-conio-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-namedpipe_45d0ade8ee64997f     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-namedpipe_45d0ade8ee64997f:  api-ms-win-core-namedpipe-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-sysinfo-l_b7a5bdc6f2238ba5     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-sysinfo-l_b7a5bdc6f2238ba5:  api-ms-win-core-sysinfo-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-handle-l1_eb218752f3acd08a     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-handle-l1_eb218752f3acd08a:  api-ms-win-core-handle-l1-1-0.dll
(f)    CSI F Mark Bad Type    0x000000DE     f!api-ms-win-core-librarylo_8dba425bf95afa18     amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2     
(fix)    CSI F Mark Bad Type    CSI Registry Item Repaired    Wrote  amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2\f!api-ms-win-core-librarylo_8dba425bf95afa18:  api-ms-win-core-libraryloader-l1-1-0.dll

...TBC...