Tweaking.com Support Forums

Main Forum => General Computer Support => Topic started by: Lady on July 28, 2015, 11:41:58 am

Title: (Solved) Problems with Lenovo bloatware
Post by: Lady on July 28, 2015, 11:41:58 am

Hello,

I'd like to ask for help with removing bloatware from my brand-new Lenovo laptop. I tried to find info online about whether I could/should remove programs but couldn't find much. So I just did what seemed right :(. Now I find myself with a few problems I don't know how to solve. I thought about re-installation (without using the recovery key!) but maybe you can help me avoid that. :)

My main reason to remove all bloatware is that I don't want ANY connection to some cloud or company online through these programs.

I used Revo Uninstaller but I don't understand why some programs don't appear in Revo. Not only some of the bloatware doesn't show, also programs like 7-zip or Bonjour (can I delete the latter? I have Windows 8.1 on my laptop and don't have Apple products. This goes for the other 2 Apple programs as well, see my screenshots).

I have made several screenshots of various places where programs show. I assume they speak for themselves. Can somebody please tell me which remaining bloatware I can delete and how, in case they don't show in Revo? Like Lenovo Messenger and Veriface.

The only program I'd like to keep are the User Manuals. They might be handy, I suppose. Please feel free to add comments about other programs you see that I don't need. The Van Dale programs are my dictionaries and they're staying. :D

Lenovo Photo Master and SHAREit I uninstalled but still show (why?) but they are empty folders.

There are two Windows Driver Packages from Lenovo that I don't dare remove as drivers are like super-essential parts to me as a lay-woman. :) Can they go too?

A lot of questions. I do hope someone will go through the trouble of telling me what to do.

Thank you for being there! :D

Lady

Title: Re: Problems with Lenovo bloatware
Post by: Shane on July 28, 2015, 03:14:45 pm

Honestly it will take you longer to uninstall all that crap then it would to do a fresh install lol

Another option you can try, and you can always go back to your install from the recovery if you like. But Windows 10 is due out tomorrow and it is a free upgrade for systems like yours. i already got the rtm and put it on a couple of my customers machines for testing and they all updated and activated just fine.

So it might be worth, so you can at least try it, having the windows 10 upgrade happen, one of the options during the upgrade is to transfer your files OR transfer nothing at all and start fresh, you should do it that way.

As a fall back, say you dont like it, you can restore the system to factory default and start uninstalling everything lol

Shane

Title: Re: Problems with Lenovo bloatware
Post by: Boggin on July 28, 2015, 04:30:12 pm

The reason why the free version of Revo doesn't see all programs is because it only picks up on 32 bit programs.

A workaround is to use the trial Pro version which does, but I use IOBit Uninstaller which sees the lot. http://www.majorgeeks.com/files/details/iobit_uninstaller.html

Decrapifier is a program that can list what to dump and StartUpLite is a program which can tell you if you have unnecessary programs in your Startup Menu - but don't disable these if you intend to uninstall them as you will be left with orphaned files and the items will remain in your msconfig/Startup list.

http://www.pcdecrapifier.com/download

https://www.malwarebytes.org/startuplite/

You should also uninstall Superfish if your computer has it installed as it was supposed to have been removed in newer Lenovo computers.

http://www.theguardian.com/technology/2015/mar/09/lenovo-superfish-third-party-apps

https://support.lenovo.com/us/en/product_security/superfish_uninstall

Title: Re: Problems with Lenovo bloatware
Post by: Lady on July 29, 2015, 03:29:17 am

Thanks a lot, guys!! I really appreciate your help. Have to figure out what is best to do..... BTW, Superfish had been detected by MBAM and BullGuard right away.

Is there a possibility to re-install 8.1 without using the recovery key and avoid all the bloatware to re-appear? I have its licence key.

Shane, are you going to post something about the privacy issues with Windows 10? Do you know if it is possible to make a local account again and prevent ANY of my data to be sent ANYWHERE?  :D :D :D

Title: Re: Problems with Lenovo bloatware
Post by: Shane on July 29, 2015, 06:24:43 pm

I have windows 10 installed in vmware, when it asks me to make a microsoft account I just skip it, then it lets me make a local account :-)

Windows 8 should auto pull the key from the system bios, so you should be fine. Heck i think 10 will as well.

Shane

Title: Re: Problems with Lenovo bloatware
Post by: Julian on July 29, 2015, 07:00:19 pm

Quote from: Shane on July 29, 2015, 06:24:43 pm

I have windows 10 installed in vmware, when it asks me to make a microsoft account I just skip it, then it lets me make a local account :-)

Windows 8 should auto pull the key from the system bios, so you should be fine. Heck i think 10 will as well.

Shane

yeah something annoying on windows 10 is that when you create a local account and login to an app with your email it will auto set you up for skydrive bs lol... I'm gonna find a work around to make that disabled

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 17, 2015, 03:22:00 am

Okay guys, I managed to get rid of almost all the bloatware and so far so good, the laptop is still functioning, haha.

It was superannoying that there is just no information on the web about whether a program is necessary or can be deleted. I find that Lenovo itself should explain on their site what all these programs are. I saw many people asking questions about this but there weren't many answers. And there were programs that needed to stay like the Synaptics Pointing Device Driver  :shocked:! Who knows what that is if you're not an IT person like you!!

So, pffff, just 3 programs left for you to say whether they can stay or go.

The first I'm most concerned about as it might have to do with sending my data somewhere.
The second I think has to stay for as far as I was able to find out.
The third I have no idea.

Can you help out?

Title: Re: Problems with Lenovo bloatware
Post by: Boggin on August 17, 2015, 04:45:51 am

I think I'd be inclined to uninstall the Customer Feedback Program.

As for the other two, nothing of any value came up on a Google search for them, but any Contollers should be left alone as they may be required for some adapters and may be Lenovo specific.

You may want to have a read of this article to see if you are affected as it looks like more spyware from Lenovo. https://support.lenovo.com/us/en/documents/ht073614?tabName=Solutions

Title: Re: Problems with Lenovo bloatware
Post by: Samson on August 17, 2015, 10:36:26 am

You may find this article interesting......

http://news.filehippo.com/2015/08/lenovo-busted-installing-irremovable-spyware-software-computers/

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 17, 2015, 11:16:37 am

Thanks, Samson!

That's pretty scary. I was advised to buy a Lenovo laptop by the head of the technical dept. of my PC shop as being the best laptop available at the moment for its internal stability and high quality materials on the outside. Did I make a mistake then?  :confused:

The article doesn't give any links to the BIOS updates and that's way over my head anyway, so I need you guys to help me out with that as well. Anyone in for that?   :smiley:

Title: Re: Problems with Lenovo bloatware
Post by: Samson on August 17, 2015, 11:21:09 am

Here you go....

https://support.lenovo.com/us/en/product_security/lse_bios_notebook

If your model is mentioned, then wait for expert advice from Shane, Julian or Boggin on how to proceed  :wink:

Title: Re: Problems with Lenovo bloatware
Post by: Julian on August 17, 2015, 11:22:11 am

I love asus for gaming and everyday computer and building computers for customers.
 I like Lenovo's for everyday office and business stuff or for school work.

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 17, 2015, 11:40:29 am

I'm not sure, I have a Z50-70. It says in the list Z41-70/Z51-70. Does that mean only those two models or everything in between?

This is a very important issue. I suggest we make this into a new topic for everyone with a Lenovo pc to find easily. Shall I open a new topic?

Title: Re: Problems with Lenovo bloatware
Post by: Samson on August 17, 2015, 11:51:06 am

Quote from: Lady on August 17, 2015, 11:40:29 am

I'm not sure, I have a Z50-70. It says in the list Z41-70/Z51-70. Does that mean only those two models or everything in between?

Following the links through to the bios update, it states....."Lenovo Z41-70, Z51-70"

Looks like you dodged a bullet  :wink:

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 17, 2015, 01:25:57 pm

Yoohooooooooooooooo!!!!!   

Could use a bit of good news. :S

But.......I downloaded the ReadMe file and there it says:

"This package updates the basic input/output system (BIOS) on IdeaPad Z41-70/Z51-70."

Should I do the BIOS update anyways to be sure? Or can I find out if I have this Lenovo Service Engine?

Again I suggest a new post. What's the best name to give it? How to remove Lenovo spyware?

Shane, Julian, Boggin?

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 17, 2015, 01:29:50 pm

Boggin, as regards your link: You may want to have a read of this article to see if you are affected as it looks like more spyware from Lenovo. https://support.lenovo.com/us/en/documents/ht073614?tabName=Solutions

I have Windows 8.1 on my laptop, so it seems this one doesn't affect me. Correct me if I'm wrong.

Title: Re: Problems with Lenovo bloatware
Post by: Boggin on August 17, 2015, 02:13:16 pm

My link seems a little ambiguous in that it says if you have loaded LSC or Using Win 7 Pre-Loaded Image, but lower down the page says Applies to Win 7 and while it lists systems, says that it is not restricted to those systems.

Have you checked Task Scheduler to see if anything related is in there ?

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 18, 2015, 06:25:42 am

What a smart idea, Boggin!

It's the first time I see the task scheduler. I assume all the Microsoft\Windows tasks are okay?

The only Lenovo task is indeed this Customer Feedback Program, scheduled EVERY DAY! But this is not a normal program, I can't find it in Programs and Features nor in Revo Uninstaller Pro. It seems to be an application? See screenshot. How do I delete that?

I also looked for the Lenovo Service Engine elsewhere, searched the whole laptop on these words without results.

Awaiting instructions.  :smiley:

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 18, 2015, 06:47:45 am

Okay, I'm an IT-amateur, so I had to be a bit resourceful.  :smiley:

On the Lenovo site about deleting the LSE it says under Windows 8.1 that these files shall be deleted:

Deletes all files installed by the LSE module, which include
C:\windows\system32\wpbbin.exe
C:\windows\system32\LenovoUpdate.exe
C:\windows\system32\LenovoCheck.exe


I checked in my Windows Explorer and don't see these files. Is that conclusive evidence that I don't have this LSE?

Title: Re: Problems with Lenovo bloatware
Post by: Boggin on August 18, 2015, 07:17:19 am

I don't see any reason why you shouldn't disable those in Task Scheduler - I know I wouldn't want my laptop reporting back every day, but check to see if it has any impact on performance.

I would say that not finding those files would suggest that you didn't have LSE.

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 18, 2015, 08:32:54 am

No, I certainly don't want that in my task scheduler! But the problem is that I don't know how to disable it AND if I uninstall the whole application, maybe I shouldn't disable it in the scheduler now because then rest files might be left behind, similar to something I just read about uninstalling files. I'm sorry, that is supervague, but maybe you know what I'm trying to say.

So, how do I get rid of this Customer Feedback Program in total? Do you know?

Title: Re: Problems with Lenovo bloatware
Post by: Boggin on August 18, 2015, 09:19:46 am

Yes, if you uninstall a program that you have unchecked in msconfig, it will leave orphaned files.

As you don't have this "phone home" program to get hold of to uninstall, click on them in Task Scheduler and select Disable.

That is what I did with GWX as that checked MS at certain times to see if your upgrade was ready and displayed the times it was triggered.

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 18, 2015, 01:59:15 pm

That's right, it was the msconfig thing! Now I remember. :S

But listen to this, Boggin! I did it! I removed this whole freaking Customer Feedback Program. I didn't know I had to double-click the program in the task scheduler, but once I figured that out, I saw the whole path that it had in program files. See screenshot. I got a hunch to go overthere instead of just disabling it in the scheduler. I went overthere, right-clicked on CFP and then I saw the option de-install with Revo Uninstaller Pro. I clicked that to see what would happen. And Revo found remnants! (I tried the search function in Revo before with no results.) See screenshot (it says "found left-behind files and folders). So I could remove it after all! So this might be good to know, if there's no program file to be seen in Programs and Features or in Revo that Revo can still find it this way. Or did I just invent the wheel, hahaha.

The odd thing was that after I de-installed it, the bloody thing was STILL in the task scheduler and there I didn't just disable it, but REMOVED it. I was DONE with it.  :teeth:

ALL bloatware and other nasty stuff gone now. AND I did the Repair All In One twice to make sure EVERYTHING is superfine now.

Aren't I the COOLEST!!!  :artist:

GRATEFUL!!!  THANK YOU for your help!!! :cheesy: :cheesy: :cheesy:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 18, 2015, 02:47:16 pm

That's great news, Lady.

Open a Command prompt (Admin) and enter sfc /scannow and if that comes back with no violations then it would be prudent to create a full external system image and keep that as a fall back should you ever need to factory reset, which you can then restore with to bring it back the way you want it.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 19, 2015, 03:28:04 am

I did the scan and it says it found corrupted files some of which it couldn't fix. What should I do now? Do you want to see the log?
I'm disappointed.......after all my efforts, still errors.....  :sad:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 19, 2015, 03:41:57 am

That is disappointing.

At the admin command prompt enter findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt and that will put an icon onto the Desktop.

Double click on that and it will open Notepad with the CBS Log which you can then copy & paste into the reply box.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 19, 2015, 04:49:43 am

The notepad from the icon was empty. ??
I found the CBS log in Windows\Logs\. See below. I assume that is the same one. There are als 3 CBS persist logs. Do you want those too?

2015-08-19 11:43:31, Info                  CBS    TI: --- Initializing Trusted Installer ---
2015-08-19 11:43:31, Info                  CBS    TI: Last boot time: 2015-08-18 22:04:50.491
2015-08-19 11:43:31, Info                  CBS    TI: Anticipating that shutdown processing will be required.
2015-08-19 11:43:31, Info                  CBS    Starting TrustedInstaller initialization.
2015-08-19 11:43:31, Info                  CBS    Ending TrustedInstaller initialization.
2015-08-19 11:43:31, Info                  CBS    Starting the TrustedInstaller main loop.
2015-08-19 11:43:31, Info                  CBS    TrustedInstaller service starts successfully.
2015-08-19 11:43:31, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
2015-08-19 11:43:31, Info                  CBS    Startup processing thread terminated normally
2015-08-19 11:43:31, Info                  CBS    Starting TiWorker initialization.
2015-08-19 11:43:31, Info                  CBS    Ending TiWorker initialization.
2015-08-19 11:43:31, Info                  CBS    Starting the TiWorker main loop.
2015-08-19 11:43:31, Info                  CBS    TiWorker starts successfully.
2015-08-19 11:43:31, Info                  CBS    TiWorker: Client requests SFP repair object.
2015-08-19 11:43:31, Info                  CBS    Universal Time is: 2015-08-19 09:43:31.345
2015-08-19 11:43:31, Info                  CBS    Loaded Servicing Stack v6.3.9600.17709 with Core: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17709_none_fa7932f59afc2e40\cbscore.dll
2015-08-19 11:43:31, Info                  CSI    00000001@2015/8/19:09:43:31.360 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff954197f19 @0x7ff954474984 @0x7ff9544741bb @0x7ff75cf4d69a @0x7ff75cf4e275 @0x7ff97cd42053)
2015-08-19 11:43:31, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2015-08-19 11:43:31, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2015-08-19 11:43:31, Info                  CBS    SQM: Requesting upload of all unsent reports.
2015-08-19 11:43:31, Info                  CBS    SQM: Failed to start upload with file pattern: C:\windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2015-08-19 11:43:31, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2015-08-19 11:43:31, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\windows\servicing\sqm\*_all.sqm, flags: 0x6
2015-08-19 11:43:31, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2015-08-19 11:43:31, Info                  CBS    NonStart: Set pending store consistency check.
2015-08-19 11:43:31, Info                  CSI    00000002@2015/8/19:09:43:31.470 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ff954197f19 @0x7ff978208a65 @0x7ff978208bb2 @0x7ff75cf4cd89 @0x7ff75cf4e28c @0x7ff97cd42053)
2015-08-19 11:43:32, Info                  CSI    00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x818b66db20
2015-08-19 11:43:32, Info                  CSI    00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2015-08-19 11:43:32, Info                  CSI    00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x260
2015-08-19 11:43:32, Info                  CSI    00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2015-08-19 11:43:32, Info                  CSI    00000007@2015/8/19:09:43:32.360 Beginning NT transaction commit...
2015-08-19 11:43:32, Info                  CSI    00000008@2015/8/19:09:43:32.360 CSI perf trace:
CSIPERF:TXCOMMIT;362
2015-08-19 11:43:32, Info                  CSI    00000009 CSI Store 556388321232 (0x000000818b5407d0) initialized
2015-08-19 11:43:35, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:35, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:38, Info                  CSI    0000000c [SR] Verify complete
2015-08-19 11:43:38, Info                  CSI    0000000d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:38, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:41, Info                  CSI    0000000f [SR] Verify complete
2015-08-19 11:43:42, Info                  CSI    00000010 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:42, Info                  CSI    00000011 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:45, Info                  CSI    00000012 [SR] Verify complete
2015-08-19 11:43:45, Info                  CSI    00000013 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:45, Info                  CSI    00000014 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:48, Info                  CSI    00000015 [SR] Verify complete
2015-08-19 11:43:48, Info                  CSI    00000016 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:48, Info                  CSI    00000017 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:51, Info                  CSI    00000018 [SR] Verify complete
2015-08-19 11:43:51, Info                  CSI    00000019 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:51, Info                  CSI    0000001a [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:54, Info                  CSI    0000001b [SR] Verify complete
2015-08-19 11:43:55, Info                  CSI    0000001c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:55, Info                  CSI    0000001d [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:57, Info                  CSI    0000001e [SR] Verify complete
2015-08-19 11:43:58, Info                  CSI    0000001f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:58, Info                  CSI    00000020 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:00, Info                  CSI    00000021 [SR] Verify complete
2015-08-19 11:44:00, Info                  CSI    00000022 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:00, Info                  CSI    00000023 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:04, Info                  CSI    00000024 [SR] Verify complete
2015-08-19 11:44:04, Info                  CSI    00000025 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:04, Info                  CSI    00000026 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:07, Info                  CSI    00000027 [SR] Verify complete
2015-08-19 11:44:07, Info                  CSI    00000028 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:07, Info                  CSI    00000029 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:10, Info                  CSI    0000002a [SR] Verify complete
2015-08-19 11:44:10, Info                  CSI    0000002b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:10, Info                  CSI    0000002c [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:13, Info                  CSI    0000002d [SR] Verify complete
2015-08-19 11:44:13, Info                  CSI    0000002e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:13, Info                  CSI    0000002f [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:16, Info                  CSI    00000030 [SR] Verify complete
2015-08-19 11:44:16, Info                  CSI    00000031 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:16, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:19, Info                  CSI    00000033 [SR] Verify complete
2015-08-19 11:44:19, Info                  CSI    00000034 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:19, Info                  CSI    00000035 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:22, Info                  CSI    00000036 [SR] Verify complete
2015-08-19 11:44:22, Info                  CSI    00000037 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:22, Info                  CSI    00000038 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:25, Info                  CSI    00000039 [SR] Verify complete
2015-08-19 11:44:25, Info                  CSI    0000003a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:25, Info                  CSI    0000003b [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:28, Info                  CSI    0000003c [SR] Verify complete
2015-08-19 11:44:28, Info                  CSI    0000003d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:28, Info                  CSI    0000003e [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:31, Info                  CSI    0000003f [SR] Verify complete
2015-08-19 11:44:31, Info                  CSI    00000040 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:31, Info                  CSI    00000041 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:34, Info                  CSI    00000042 [SR] Verify complete
2015-08-19 11:44:35, Info                  CSI    00000043 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:35, Info                  CSI    00000044 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:38, Info                  CSI    00000045 [SR] Verify complete
2015-08-19 11:44:38, Info                  CSI    00000046 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:38, Info                  CSI    00000047 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:41, Info                  CSI    00000048 [SR] Verify complete
2015-08-19 11:44:41, Info                  CSI    00000049 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:41, Info                  CSI    0000004a [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:44, Info                  CSI    0000004b [SR] Verify complete
2015-08-19 11:44:44, Info                  CSI    0000004c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:44, Info                  CSI    0000004d [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:47, Info                  CSI    0000004e [SR] Verify complete
2015-08-19 11:44:47, Info                  CSI    0000004f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:47, Info                  CSI    00000050 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:49, Info                  CSI    00000051 [SR] Verify complete
2015-08-19 11:44:49, Info                  CSI    00000052 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:49, Info                  CSI    00000053 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:52, Info                  CSI    00000054 [SR] Verify complete
2015-08-19 11:44:52, Info                  CSI    00000055 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:52, Info                  CSI    00000056 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:55, Info                  CSI    00000057 [SR] Verify complete
2015-08-19 11:44:55, Info                  CSI    00000058 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:55, Info                  CSI    00000059 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:58, Info                  CSI    0000005a [SR] Verify complete
2015-08-19 11:44:58, Info                  CSI    0000005b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:58, Info                  CSI    0000005c [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:01, Info                  CSI    0000005d [SR] Verify complete
2015-08-19 11:45:01, Info                  CSI    0000005e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:01, Info                  CSI    0000005f [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:04, Info                  CSI    00000060 [SR] Verify complete
2015-08-19 11:45:04, Info                  CSI    00000061 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:04, Info                  CSI    00000062 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:07, Info                  CSI    00000063 [SR] Verify complete
2015-08-19 11:45:07, Info                  CSI    00000064 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:07, Info                  CSI    00000065 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:09, Info                  CSI    00000066 [SR] Verify complete
2015-08-19 11:45:09, Info                  CSI    00000067 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:09, Info                  CSI    00000068 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:12, Info                  CSI    00000069 [SR] Verify complete
2015-08-19 11:45:12, Info                  CSI    0000006a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:12, Info                  CSI    0000006b [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:15, Info                  CSI    0000006c [SR] Verify complete
2015-08-19 11:45:15, Info                  CSI    0000006d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:15, Info                  CSI    0000006e [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:18, Info                  CSI    0000006f [SR] Verify complete
2015-08-19 11:45:18, Info                  CSI    00000070 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:18, Info                  CSI    00000071 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:21, Info                  CSI    00000072 [SR] Verify complete
2015-08-19 11:45:21, Info                  CSI    00000073 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:21, Info                  CSI    00000074 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:24, Info                  CSI    00000075 [SR] Verify complete
2015-08-19 11:45:24, Info                  CSI    00000076 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:24, Info                  CSI    00000077 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:27, Info                  CSI    00000078 [SR] Verify complete
2015-08-19 11:45:27, Info                  CSI    00000079 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:27, Info                  CSI    0000007a [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:30, Info                  CSI    0000007b [SR] Verify complete
2015-08-19 11:45:30, Info                  CSI    0000007c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:30, Info                  CSI    0000007d [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:32, Info                  CSI    0000007e [SR] Verify complete
2015-08-19 11:45:32, Info                  CSI    0000007f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:32, Info                  CSI    00000080 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:35, Info                  CSI    00000081 [SR] Verify complete
2015-08-19 11:45:35, Info                  CSI    00000082 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:35, Info                  CSI    00000083 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:38, Info                  CSI    00000084 [SR] Verify complete
2015-08-19 11:45:38, Info                  CSI    00000085 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:38, Info                  CSI    00000086 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:41, Info                  CSI    00000087 [SR] Verify complete
2015-08-19 11:45:41, Info                  CSI    00000088 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:41, Info                  CSI    00000089 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:44, Info                  CSI    0000008a [SR] Verify complete
2015-08-19 11:45:44, Info                  CSI    0000008b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:44, Info                  CSI    0000008c [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:47, Info                  CSI    0000008d [SR] Verify complete
2015-08-19 11:45:47, Info                  CSI    0000008e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:47, Info                  CSI    0000008f [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:50, Info                  CSI    00000090 [SR] Verify complete
2015-08-19 11:45:50, Info                  CSI    00000091 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:50, Info                  CSI    00000092 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:53, Info                  CSI    00000093 [SR] Verify complete
2015-08-19 11:45:53, Info                  CSI    00000094 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:53, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:56, Info                  CSI    00000096 [SR] Verify complete
2015-08-19 11:45:56, Info                  CSI    00000097 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:56, Info                  CSI    00000098 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:58, Info                  CSI    00000099 [SR] Verify complete
2015-08-19 11:45:58, Info                  CSI    0000009a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:58, Info                  CSI    0000009b [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:01, Info                  CSI    0000009c [SR] Verify complete
2015-08-19 11:46:01, Info                  CSI    0000009d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:01, Info                  CSI    0000009e [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:04, Info                  CSI    0000009f [SR] Verify complete
2015-08-19 11:46:04, Info                  CSI    000000a0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:04, Info                  CSI    000000a1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:08, Info                  CSI    000000a2 Ignoring duplicate ownership for directory [l:76{38}]"\??\C:\windows\System32\Macromed\Flash" in component Adobe-Flash-For-Windows, Version = 7.3.9600.18008, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:46:09, Info                  CSI    000000a3 [SR] Verify complete
2015-08-19 11:46:09, Info                  CSI    000000a4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:09, Info                  CSI    000000a5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:12, Info                  CSI    000000a6 [SR] Verify complete
2015-08-19 11:46:12, Info                  CSI    000000a7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:12, Info                  CSI    000000a8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:14, Info                  CSI    000000a9 [SR] Verify complete
2015-08-19 11:46:14, Info                  CSI    000000aa [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:14, Info                  CSI    000000ab [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:17, Info                  CSI    000000ac [SR] Verify complete
2015-08-19 11:46:17, Info                  CSI    000000ad [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:17, Info                  CSI    000000ae [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:20, Info                  CSI    000000af [SR] Verify complete
2015-08-19 11:46:20, Info                  CSI    000000b0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:20, Info                  CSI    000000b1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:23, Info                  CSI    000000b2 [SR] Verify complete
2015-08-19 11:46:23, Info                  CSI    000000b3 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:23, Info                  CSI    000000b4 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:27, Info                  CSI    000000b5 [SR] Verify complete
2015-08-19 11:46:27, Info                  CSI    000000b6 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:27, Info                  CSI    000000b7 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:30, Info                  CSI    000000b8 [SR] Verify complete
2015-08-19 11:46:30, Info                  CSI    000000b9 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:30, Info                  CSI    000000ba [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:33, Info                  CSI    000000bb [SR] Verify complete
2015-08-19 11:46:33, Info                  CSI    000000bc [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:33, Info                  CSI    000000bd [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:35, Info                  CSI    000000be [SR] Verify complete
2015-08-19 11:46:36, Info                  CSI    000000bf [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:36, Info                  CSI    000000c0 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:38, Info                  CSI    000000c1 [SR] Verify complete
2015-08-19 11:46:38, Info                  CSI    000000c2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:38, Info                  CSI    000000c3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:41, Info                  CSI    000000c4 [SR] Verify complete
2015-08-19 11:46:41, Info                  CSI    000000c5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:41, Info                  CSI    000000c6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:44, Info                  CSI    000000c7 [SR] Verify complete
2015-08-19 11:46:44, Info                  CSI    000000c8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:44, Info                  CSI    000000c9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:46, Info                  CSI    000000ca [SR] Verify complete
2015-08-19 11:46:46, Info                  CSI    000000cb [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:46, Info                  CSI    000000cc [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:49, Info                  CSI    000000cd [SR] Verify complete
2015-08-19 11:46:49, Info                  CSI    000000ce [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:49, Info                  CSI    000000cf [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:52, Info                  CSI    000000d0 [SR] Verify complete
2015-08-19 11:46:52, Info                  CSI    000000d1 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:52, Info                  CSI    000000d2 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:55, Info                  CSI    000000d3 [SR] Verify complete
2015-08-19 11:46:55, Info                  CSI    000000d4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:55, Info                  CSI    000000d5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:58, Info                  CSI    000000d6 [SR] Verify complete
2015-08-19 11:46:58, Info                  CSI    000000d7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:58, Info                  CSI    000000d8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:01, Info                  CSI    000000d9 [SR] Verify complete
2015-08-19 11:47:01, Info                  CSI    000000da [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:01, Info                  CSI    000000db [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:04, Info                  CSI    000000dc [SR] Verify complete
2015-08-19 11:47:04, Info                  CSI    000000dd [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:04, Info                  CSI    000000de [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:07, Info                  CSI    000000df [SR] Verify complete
2015-08-19 11:47:07, Info                  CSI    000000e0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:07, Info                  CSI    000000e1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:10, Info                  CSI    000000e2 [SR] Verify complete
2015-08-19 11:47:10, Info                  CSI    000000e3 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:10, Info                  CSI    000000e4 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:13, Info                  CSI    000000e5 [SR] Verify complete
2015-08-19 11:47:13, Info                  CSI    000000e6 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:13, Info                  CSI    000000e7 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:16, Info                  CSI    000000e8 [SR] Verify complete
2015-08-19 11:47:16, Info                  CSI    000000e9 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:16, Info                  CSI    000000ea [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:19, Info                  CSI    000000eb [SR] Verify complete
2015-08-19 11:47:19, Info                  CSI    000000ec [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:19, Info                  CSI    000000ed [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:22, Info                  CSI    000000ee [SR] Verify complete
2015-08-19 11:47:23, Info                  CSI    000000ef [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:23, Info                  CSI    000000f0 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:25, Info                  CSI    000000f1 [SR] Verify complete
2015-08-19 11:47:25, Info                  CSI    000000f2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:25, Info                  CSI    000000f3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:28, Info                  CSI    000000f4 [SR] Verify complete
2015-08-19 11:47:28, Info                  CSI    000000f5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:28, Info                  CSI    000000f6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:31, Info                  CSI    000000f7 [SR] Verify complete
2015-08-19 11:47:31, Info                  CSI    000000f8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:31, Info                  CSI    000000f9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:35, Info                  CSI    000000fa [SR] Verify complete
2015-08-19 11:47:35, Info                  CSI    000000fb [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:35, Info                  CSI    000000fc [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:40, Info                  CSI    000000fd [SR] Verify complete
2015-08-19 11:47:40, Info                  CSI    000000fe [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:40, Info                  CSI    000000ff [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:45, Info                  CSI    00000100 [SR] Verify complete
2015-08-19 11:47:45, Info                  CSI    00000101 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:45, Info                  CSI    00000102 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:48, Info                  CSI    00000103 [SR] Verify complete
2015-08-19 11:47:48, Info                  CSI    00000104 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:48, Info                  CSI    00000105 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:52, Info                  CSI    00000106 [SR] Verify complete
2015-08-19 11:47:52, Info                  CSI    00000107 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:52, Info                  CSI    00000108 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:56, Info                  CSI    00000109 [DIRSD OWNER WARNING] Directory [ml:520{260},l:88{44}]"\??\C:\windows\Help\Windows\IndexStore\en-US" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:56, Info                  CSI    0000010a [DIRSD OWNER WARNING] Directory [ml:520{260},l:50{25}]"\??\C:\windows\Help\en-US" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:56, Info                  CSI    0000010b [DIRSD OWNER WARNING] Directory [ml:520{260},l:92{46}]"\??\C:\windows\Help\Windows\ContentStore\en-US" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000010c [DIRSD OWNER WARNING] Directory [ml:520{260},l:48{24}]"\??\C:\windows\Help\Help" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000010d [DIRSD OWNER WARNING] Directory [ml:520{260},l:80{40}]"\??\C:\windows\Help\Windows\ContentStore" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000010e [DIRSD OWNER WARNING] Directory [ml:520{260},l:58{29}]"\??\C:\windows\Help\Corporate" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000010f [DIRSD OWNER WARNING] Directory [ml:520{260},l:72{36}]"\??\C:\windows\Help\OEM\ContentStore" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000110 [DIRSD OWNER WARNING] Directory [ml:520{260},l:54{27}]"\??\C:\windows\Help\Windows" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000111 [DIRSD OWNER WARNING] Directory [ml:520{260},l:68{34}]"\??\C:\windows\Help\OEM\IndexStore" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000112 [DIRSD OWNER WARNING] Directory [ml:520{260},l:76{38}]"\??\C:\windows\Help\Windows\IndexStore" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000113 [DIRSD OWNER WARNING] Directory [ml:520{260},l:46{23}]"\??\C:\windows\Help\OEM" is not owned but specifies SDDL in component Microsoft-Windows-Assistance-CollectionFiles-Help, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000114 Ignoring duplicate ownership for directory [l:46{23}]"\??\C:\windows\Help\OEM" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000115 Ignoring duplicate ownership for directory [l:68{34}]"\??\C:\windows\Help\OEM\IndexStore" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000116 Ignoring duplicate ownership for directory [l:72{36}]"\??\C:\windows\Help\OEM\ContentStore" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000117 Ignoring duplicate ownership for directory [l:54{27}]"\??\C:\windows\Help\Windows" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000118 Ignoring duplicate ownership for directory [l:76{38}]"\??\C:\windows\Help\Windows\IndexStore" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    00000119 Ignoring duplicate ownership for directory [l:80{40}]"\??\C:\windows\Help\Windows\ContentStore" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000011a Ignoring duplicate ownership for directory [l:58{29}]"\??\C:\windows\Help\Corporate" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000011b Ignoring duplicate ownership for directory [l:48{24}]"\??\C:\windows\Help\Help" in component Microsoft-Windows-Assistance-CollectionFiles-Help, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:57, Info                  CSI    0000011c [DIRSD OWNER WARNING] Directory [ml:520{260},l:90{45}]"\??\C:\windows\diagnostics\system\Audio\nl-NL" is not owned but specifies SDDL in component Microsoft-Windows-AudioDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:58, Info                  CSI    0000011d [DIRSD OWNER WARNING] Directory [ml:520{260},l:88{44}]"\??\C:\windows\diagnostics\system\AERO\nl-NL" is not owned but specifies SDDL in component Microsoft-Windows-AeroDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    0000011e [DIRSD OWNER WARNING] Directory [ml:520{260},l:90{45}]"\??\C:\windows\diagnostics\system\Audio\en-US" is not owned but specifies SDDL in component Microsoft-Windows-AudioDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    0000011f [DIRSD OWNER WARNING] Directory [ml:520{260},l:88{44}]"\??\C:\windows\diagnostics\system\AERO\en-US" is not owned but specifies SDDL in component Microsoft-Windows-AeroDiagnostic.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    00000120 [DIRSD OWNER WARNING] Directory [ml:520{260},l:78{39}]"\??\C:\windows\apppatch\Custom\Custom64" is not owned but specifies SDDL in component Microsoft-Windows-Application-Experience-Infrastructure, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    00000121 [DIRSD OWNER WARNING] Directory [ml:520{260},l:60{30}]"\??\C:\windows\apppatch\Custom" is not owned but specifies SDDL in component Microsoft-Windows-Application-Experience-Infrastructure, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    00000122 [DIRSD OWNER WARNING] Directory [ml:520{260},l:68{34}]"\??\C:\windows\apppatch\AppPatch64" is not owned but specifies SDDL in component Microsoft-Windows-Application-Experience-Infrastructure, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:47:59, Info                  CSI    00000123 [SR] Verify complete
2015-08-19 11:47:59, Info                  CSI    00000124 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:59, Info                  CSI    00000125 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:03, Info                  CSI    00000126 Ignoring duplicate ownership for directory [l:46{23}]"\??\C:\windows\SchCache" in component Microsoft-Windows-Active-Directory-Services-Interface-LDAP-Provider, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:03, Info                  CSI    00000127 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17998, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:04, Info                  CSI    00000128 [SR] Verify complete
2015-08-19 11:48:04, Info                  CSI    00000129 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:04, Info                  CSI    0000012a [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:10, Info                  CSI    0000012b Ignoring duplicate ownership for directory [l:72{36}]"\??\C:\windows\resources\themes\aero" in component Microsoft-Windows-aero, Version = 6.3.9600.17284, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:10, Info                  CSI    0000012c [DIRSD OWNER WARNING] Directory [ml:520{260},l:84{42}]"\??\C:\windows\resources\themes\aero\en-US" is not owned but specifies SDDL in component Microsoft-Windows-aero.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:10, Info                  CSI    0000012d Ignoring duplicate ownership for directory [l:84{42}]"\??\C:\windows\resources\themes\aero\en-US" in component Microsoft-Windows-aero.Resources, Version = 6.3.9600.17031, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:11, Info                  CSI    0000012e [DIRSD OWNER WARNING] Directory [ml:520{260},l:66{33}]"\??\C:\windows\System32\AppLocker" is not owned but specifies SDDL in component Microsoft-Windows-AppID, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:11, Info                  CSI    0000012f [DIRSD OWNER WARNING] Directory [ml:520{260},l:78{39}]"\??\C:\windows\diagnostics\system\Audio" is not owned but specifies SDDL in component Microsoft-Windows-AudioDiagnostic, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:12, Info                  CSI    00000130 [DIRSD OWNER WARNING] Directory [ml:520{260},l:76{38}]"\??\C:\windows\diagnostics\system\AERO" is not owned but specifies SDDL in component Microsoft-Windows-AeroDiagnostic, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:13, Info                  CSI    00000131 [DIRSD OWNER WARNING] Directory [ml:520{260},l:84{42}]"\??\C:\windows\resources\themes\aero\nl-NL" is not owned but specifies SDDL in component Microsoft-Windows-aero.Resources, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2015-08-19 11:48:13, Info                  CSI    00000132 Ignoring duplicate ownership for directory [l:84{42}]"\??\C:\windows\resources\themes\aero\nl-NL" in component Microsoft-Windows-aero.Resources, Version = 6.3.9600.17031, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Cul

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 19, 2015, 04:52:28 am

Oh, I tried the icon again and now it does show a log. I'm sorry, Boggin. This is all new to me. Here it is.

2015-08-19 11:43:35, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:35, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:38, Info                  CSI    0000000c [SR] Verify complete
2015-08-19 11:43:38, Info                  CSI    0000000d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:38, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:41, Info                  CSI    0000000f [SR] Verify complete
2015-08-19 11:43:42, Info                  CSI    00000010 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:42, Info                  CSI    00000011 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:45, Info                  CSI    00000012 [SR] Verify complete
2015-08-19 11:43:45, Info                  CSI    00000013 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:45, Info                  CSI    00000014 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:48, Info                  CSI    00000015 [SR] Verify complete
2015-08-19 11:43:48, Info                  CSI    00000016 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:48, Info                  CSI    00000017 [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:51, Info                  CSI    00000018 [SR] Verify complete
2015-08-19 11:43:51, Info                  CSI    00000019 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:51, Info                  CSI    0000001a [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:54, Info                  CSI    0000001b [SR] Verify complete
2015-08-19 11:43:55, Info                  CSI    0000001c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:55, Info                  CSI    0000001d [SR] Beginning Verify and Repair transaction
2015-08-19 11:43:57, Info                  CSI    0000001e [SR] Verify complete
2015-08-19 11:43:58, Info                  CSI    0000001f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:43:58, Info                  CSI    00000020 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:00, Info                  CSI    00000021 [SR] Verify complete
2015-08-19 11:44:00, Info                  CSI    00000022 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:00, Info                  CSI    00000023 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:04, Info                  CSI    00000024 [SR] Verify complete
2015-08-19 11:44:04, Info                  CSI    00000025 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:04, Info                  CSI    00000026 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:07, Info                  CSI    00000027 [SR] Verify complete
2015-08-19 11:44:07, Info                  CSI    00000028 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:07, Info                  CSI    00000029 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:10, Info                  CSI    0000002a [SR] Verify complete
2015-08-19 11:44:10, Info                  CSI    0000002b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:10, Info                  CSI    0000002c [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:13, Info                  CSI    0000002d [SR] Verify complete
2015-08-19 11:44:13, Info                  CSI    0000002e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:13, Info                  CSI    0000002f [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:16, Info                  CSI    00000030 [SR] Verify complete
2015-08-19 11:44:16, Info                  CSI    00000031 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:16, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:19, Info                  CSI    00000033 [SR] Verify complete
2015-08-19 11:44:19, Info                  CSI    00000034 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:19, Info                  CSI    00000035 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:22, Info                  CSI    00000036 [SR] Verify complete
2015-08-19 11:44:22, Info                  CSI    00000037 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:22, Info                  CSI    00000038 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:25, Info                  CSI    00000039 [SR] Verify complete
2015-08-19 11:44:25, Info                  CSI    0000003a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:25, Info                  CSI    0000003b [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:28, Info                  CSI    0000003c [SR] Verify complete
2015-08-19 11:44:28, Info                  CSI    0000003d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:28, Info                  CSI    0000003e [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:31, Info                  CSI    0000003f [SR] Verify complete
2015-08-19 11:44:31, Info                  CSI    00000040 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:31, Info                  CSI    00000041 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:34, Info                  CSI    00000042 [SR] Verify complete
2015-08-19 11:44:35, Info                  CSI    00000043 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:35, Info                  CSI    00000044 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:38, Info                  CSI    00000045 [SR] Verify complete
2015-08-19 11:44:38, Info                  CSI    00000046 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:38, Info                  CSI    00000047 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:41, Info                  CSI    00000048 [SR] Verify complete
2015-08-19 11:44:41, Info                  CSI    00000049 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:41, Info                  CSI    0000004a [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:44, Info                  CSI    0000004b [SR] Verify complete
2015-08-19 11:44:44, Info                  CSI    0000004c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:44, Info                  CSI    0000004d [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:47, Info                  CSI    0000004e [SR] Verify complete
2015-08-19 11:44:47, Info                  CSI    0000004f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:47, Info                  CSI    00000050 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:49, Info                  CSI    00000051 [SR] Verify complete
2015-08-19 11:44:49, Info                  CSI    00000052 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:49, Info                  CSI    00000053 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:52, Info                  CSI    00000054 [SR] Verify complete
2015-08-19 11:44:52, Info                  CSI    00000055 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:52, Info                  CSI    00000056 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:55, Info                  CSI    00000057 [SR] Verify complete
2015-08-19 11:44:55, Info                  CSI    00000058 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:55, Info                  CSI    00000059 [SR] Beginning Verify and Repair transaction
2015-08-19 11:44:58, Info                  CSI    0000005a [SR] Verify complete
2015-08-19 11:44:58, Info                  CSI    0000005b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:44:58, Info                  CSI    0000005c [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:01, Info                  CSI    0000005d [SR] Verify complete
2015-08-19 11:45:01, Info                  CSI    0000005e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:01, Info                  CSI    0000005f [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:04, Info                  CSI    00000060 [SR] Verify complete
2015-08-19 11:45:04, Info                  CSI    00000061 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:04, Info                  CSI    00000062 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:07, Info                  CSI    00000063 [SR] Verify complete
2015-08-19 11:45:07, Info                  CSI    00000064 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:07, Info                  CSI    00000065 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:09, Info                  CSI    00000066 [SR] Verify complete
2015-08-19 11:45:09, Info                  CSI    00000067 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:09, Info                  CSI    00000068 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:12, Info                  CSI    00000069 [SR] Verify complete
2015-08-19 11:45:12, Info                  CSI    0000006a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:12, Info                  CSI    0000006b [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:15, Info                  CSI    0000006c [SR] Verify complete
2015-08-19 11:45:15, Info                  CSI    0000006d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:15, Info                  CSI    0000006e [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:18, Info                  CSI    0000006f [SR] Verify complete
2015-08-19 11:45:18, Info                  CSI    00000070 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:18, Info                  CSI    00000071 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:21, Info                  CSI    00000072 [SR] Verify complete
2015-08-19 11:45:21, Info                  CSI    00000073 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:21, Info                  CSI    00000074 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:24, Info                  CSI    00000075 [SR] Verify complete
2015-08-19 11:45:24, Info                  CSI    00000076 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:24, Info                  CSI    00000077 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:27, Info                  CSI    00000078 [SR] Verify complete
2015-08-19 11:45:27, Info                  CSI    00000079 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:27, Info                  CSI    0000007a [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:30, Info                  CSI    0000007b [SR] Verify complete
2015-08-19 11:45:30, Info                  CSI    0000007c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:30, Info                  CSI    0000007d [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:32, Info                  CSI    0000007e [SR] Verify complete
2015-08-19 11:45:32, Info                  CSI    0000007f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:32, Info                  CSI    00000080 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:35, Info                  CSI    00000081 [SR] Verify complete
2015-08-19 11:45:35, Info                  CSI    00000082 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:35, Info                  CSI    00000083 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:38, Info                  CSI    00000084 [SR] Verify complete
2015-08-19 11:45:38, Info                  CSI    00000085 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:38, Info                  CSI    00000086 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:41, Info                  CSI    00000087 [SR] Verify complete
2015-08-19 11:45:41, Info                  CSI    00000088 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:41, Info                  CSI    00000089 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:44, Info                  CSI    0000008a [SR] Verify complete
2015-08-19 11:45:44, Info                  CSI    0000008b [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:44, Info                  CSI    0000008c [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:47, Info                  CSI    0000008d [SR] Verify complete
2015-08-19 11:45:47, Info                  CSI    0000008e [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:47, Info                  CSI    0000008f [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:50, Info                  CSI    00000090 [SR] Verify complete
2015-08-19 11:45:50, Info                  CSI    00000091 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:50, Info                  CSI    00000092 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:53, Info                  CSI    00000093 [SR] Verify complete
2015-08-19 11:45:53, Info                  CSI    00000094 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:53, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:56, Info                  CSI    00000096 [SR] Verify complete
2015-08-19 11:45:56, Info                  CSI    00000097 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:56, Info                  CSI    00000098 [SR] Beginning Verify and Repair transaction
2015-08-19 11:45:58, Info                  CSI    00000099 [SR] Verify complete
2015-08-19 11:45:58, Info                  CSI    0000009a [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:45:58, Info                  CSI    0000009b [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:01, Info                  CSI    0000009c [SR] Verify complete
2015-08-19 11:46:01, Info                  CSI    0000009d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:01, Info                  CSI    0000009e [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:04, Info                  CSI    0000009f [SR] Verify complete
2015-08-19 11:46:04, Info                  CSI    000000a0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:04, Info                  CSI    000000a1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:09, Info                  CSI    000000a3 [SR] Verify complete
2015-08-19 11:46:09, Info                  CSI    000000a4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:09, Info                  CSI    000000a5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:12, Info                  CSI    000000a6 [SR] Verify complete
2015-08-19 11:46:12, Info                  CSI    000000a7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:12, Info                  CSI    000000a8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:14, Info                  CSI    000000a9 [SR] Verify complete
2015-08-19 11:46:14, Info                  CSI    000000aa [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:14, Info                  CSI    000000ab [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:17, Info                  CSI    000000ac [SR] Verify complete
2015-08-19 11:46:17, Info                  CSI    000000ad [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:17, Info                  CSI    000000ae [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:20, Info                  CSI    000000af [SR] Verify complete
2015-08-19 11:46:20, Info                  CSI    000000b0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:20, Info                  CSI    000000b1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:23, Info                  CSI    000000b2 [SR] Verify complete
2015-08-19 11:46:23, Info                  CSI    000000b3 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:23, Info                  CSI    000000b4 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:27, Info                  CSI    000000b5 [SR] Verify complete
2015-08-19 11:46:27, Info                  CSI    000000b6 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:27, Info                  CSI    000000b7 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:30, Info                  CSI    000000b8 [SR] Verify complete
2015-08-19 11:46:30, Info                  CSI    000000b9 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:30, Info                  CSI    000000ba [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:33, Info                  CSI    000000bb [SR] Verify complete
2015-08-19 11:46:33, Info                  CSI    000000bc [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:33, Info                  CSI    000000bd [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:35, Info                  CSI    000000be [SR] Verify complete
2015-08-19 11:46:36, Info                  CSI    000000bf [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:36, Info                  CSI    000000c0 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:38, Info                  CSI    000000c1 [SR] Verify complete
2015-08-19 11:46:38, Info                  CSI    000000c2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:38, Info                  CSI    000000c3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:41, Info                  CSI    000000c4 [SR] Verify complete
2015-08-19 11:46:41, Info                  CSI    000000c5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:41, Info                  CSI    000000c6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:44, Info                  CSI    000000c7 [SR] Verify complete
2015-08-19 11:46:44, Info                  CSI    000000c8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:44, Info                  CSI    000000c9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:46, Info                  CSI    000000ca [SR] Verify complete
2015-08-19 11:46:46, Info                  CSI    000000cb [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:46, Info                  CSI    000000cc [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:49, Info                  CSI    000000cd [SR] Verify complete
2015-08-19 11:46:49, Info                  CSI    000000ce [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:49, Info                  CSI    000000cf [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:52, Info                  CSI    000000d0 [SR] Verify complete
2015-08-19 11:46:52, Info                  CSI    000000d1 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:52, Info                  CSI    000000d2 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:55, Info                  CSI    000000d3 [SR] Verify complete
2015-08-19 11:46:55, Info                  CSI    000000d4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:55, Info                  CSI    000000d5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:46:58, Info                  CSI    000000d6 [SR] Verify complete
2015-08-19 11:46:58, Info                  CSI    000000d7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:46:58, Info                  CSI    000000d8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:01, Info                  CSI    000000d9 [SR] Verify complete
2015-08-19 11:47:01, Info                  CSI    000000da [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:01, Info                  CSI    000000db [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:04, Info                  CSI    000000dc [SR] Verify complete
2015-08-19 11:47:04, Info                  CSI    000000dd [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:04, Info                  CSI    000000de [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:07, Info                  CSI    000000df [SR] Verify complete
2015-08-19 11:47:07, Info                  CSI    000000e0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:07, Info                  CSI    000000e1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:10, Info                  CSI    000000e2 [SR] Verify complete
2015-08-19 11:47:10, Info                  CSI    000000e3 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:10, Info                  CSI    000000e4 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:13, Info                  CSI    000000e5 [SR] Verify complete
2015-08-19 11:47:13, Info                  CSI    000000e6 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:13, Info                  CSI    000000e7 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:16, Info                  CSI    000000e8 [SR] Verify complete
2015-08-19 11:47:16, Info                  CSI    000000e9 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:16, Info                  CSI    000000ea [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:19, Info                  CSI    000000eb [SR] Verify complete
2015-08-19 11:47:19, Info                  CSI    000000ec [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:19, Info                  CSI    000000ed [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:22, Info                  CSI    000000ee [SR] Verify complete
2015-08-19 11:47:23, Info                  CSI    000000ef [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:23, Info                  CSI    000000f0 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:25, Info                  CSI    000000f1 [SR] Verify complete
2015-08-19 11:47:25, Info                  CSI    000000f2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:25, Info                  CSI    000000f3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:28, Info                  CSI    000000f4 [SR] Verify complete
2015-08-19 11:47:28, Info                  CSI    000000f5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:28, Info                  CSI    000000f6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:31, Info                  CSI    000000f7 [SR] Verify complete
2015-08-19 11:47:31, Info                  CSI    000000f8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:31, Info                  CSI    000000f9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:35, Info                  CSI    000000fa [SR] Verify complete
2015-08-19 11:47:35, Info                  CSI    000000fb [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:35, Info                  CSI    000000fc [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:40, Info                  CSI    000000fd [SR] Verify complete
2015-08-19 11:47:40, Info                  CSI    000000fe [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:40, Info                  CSI    000000ff [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:45, Info                  CSI    00000100 [SR] Verify complete
2015-08-19 11:47:45, Info                  CSI    00000101 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:45, Info                  CSI    00000102 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:48, Info                  CSI    00000103 [SR] Verify complete
2015-08-19 11:47:48, Info                  CSI    00000104 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:48, Info                  CSI    00000105 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:52, Info                  CSI    00000106 [SR] Verify complete
2015-08-19 11:47:52, Info                  CSI    00000107 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:52, Info                  CSI    00000108 [SR] Beginning Verify and Repair transaction
2015-08-19 11:47:59, Info                  CSI    00000123 [SR] Verify complete
2015-08-19 11:47:59, Info                  CSI    00000124 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:47:59, Info                  CSI    00000125 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:04, Info                  CSI    00000128 [SR] Verify complete
2015-08-19 11:48:04, Info                  CSI    00000129 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:04, Info                  CSI    0000012a [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:13, Info                  CSI    00000133 [SR] Verify complete
2015-08-19 11:48:13, Info                  CSI    00000134 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:13, Info                  CSI    00000135 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:19, Info                  CSI    00000138 [SR] Verify complete
2015-08-19 11:48:19, Info                  CSI    00000139 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:19, Info                  CSI    0000013a [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:25, Info                  CSI    00000145 [SR] Verify complete
2015-08-19 11:48:25, Info                  CSI    00000146 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:25, Info                  CSI    00000147 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:30, Info                  CSI    0000014e [SR] Verify complete
2015-08-19 11:48:30, Info                  CSI    0000014f [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:30, Info                  CSI    00000150 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:35, Info                  CSI    00000151 [SR] Verify complete
2015-08-19 11:48:36, Info                  CSI    00000152 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:36, Info                  CSI    00000153 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:38, Info                  CSI    00000154 [SR] Verify complete
2015-08-19 11:48:39, Info                  CSI    00000155 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:39, Info                  CSI    00000156 [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:45, Info                  CSI    00000158 [SR] Verify complete
2015-08-19 11:48:45, Info                  CSI    00000159 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:45, Info                  CSI    0000015a [SR] Beginning Verify and Repair transaction
2015-08-19 11:48:55, Info                  CSI    0000017b [SR] Verify complete
2015-08-19 11:48:55, Info                  CSI    0000017c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:48:55, Info                  CSI    0000017d [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:03, Info                  CSI    000001a1 [SR] Verify complete
2015-08-19 11:49:04, Info                  CSI    000001a2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:04, Info                  CSI    000001a3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:10, Info                  CSI    000001ab [SR] Verify complete
2015-08-19 11:49:10, Info                  CSI    000001ac [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:10, Info                  CSI    000001ad [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:18, Info                  CSI    000001b3 [SR] Verify complete
2015-08-19 11:49:18, Info                  CSI    000001b4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:18, Info                  CSI    000001b5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:27, Info                  CSI    000001c4 [SR] Verify complete
2015-08-19 11:49:27, Info                  CSI    000001c5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:27, Info                  CSI    000001c6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:34, Info                  CSI    000001d7 [SR] Verify complete
2015-08-19 11:49:34, Info                  CSI    000001d8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:34, Info                  CSI    000001d9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:41, Info                  CSI    000001df [SR] Verify complete
2015-08-19 11:49:41, Info                  CSI    000001e0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:41, Info                  CSI    000001e1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:48, Info                  CSI    000001e2 [SR] Verify complete
2015-08-19 11:49:48, Info                  CSI    000001e3 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:48, Info                  CSI    000001e4 [SR] Beginning Verify and Repair transaction
2015-08-19 11:49:56, Info                  CSI    000001e9 [SR] Verify complete
2015-08-19 11:49:56, Info                  CSI    000001ea [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:49:56, Info                  CSI    000001eb [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:02, Info                  CSI    000001f0 [SR] Verify complete
2015-08-19 11:50:02, Info                  CSI    000001f1 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:02, Info                  CSI    000001f2 [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:12, Info                  CSI    0000020c [SR] Verify complete
2015-08-19 11:50:12, Info                  CSI    0000020d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:12, Info                  CSI    0000020e [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:23, Info                  CSI    00000243 [SR] Verify complete
2015-08-19 11:50:23, Info                  CSI    00000244 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:23, Info                  CSI    00000245 [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:39, Info                  CSI    00000265 [SR] Verify complete
2015-08-19 11:50:39, Info                  CSI    00000266 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:39, Info                  CSI    00000267 [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:52, Info                  CSI    0000026c [SR] Verify complete
2015-08-19 11:50:52, Info                  CSI    0000026d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:52, Info                  CSI    0000026e [SR] Beginning Verify and Repair transaction
2015-08-19 11:50:57, Info                  CSI    00000274 [SR] Verify complete
2015-08-19 11:50:58, Info                  CSI    00000275 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:50:58, Info                  CSI    00000276 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:03, Info                  CSI    00000280 [SR] Verify complete
2015-08-19 11:51:03, Info                  CSI    00000281 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:03, Info                  CSI    00000282 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:11, Info                  CSI    0000029f [SR] Verify complete
2015-08-19 11:51:11, Info                  CSI    000002a0 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:11, Info                  CSI    000002a1 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:16, Info                  CSI    000002a3 [SR] Verify complete
2015-08-19 11:51:16, Info                  CSI    000002a4 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:16, Info                  CSI    000002a5 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:20, Info                  CSI    000002a6 [SR] Verify complete
2015-08-19 11:51:20, Info                  CSI    000002a7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:20, Info                  CSI    000002a8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:26, Info                  CSI    000002b4 [SR] Verify complete
2015-08-19 11:51:26, Info                  CSI    000002b5 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:26, Info                  CSI    000002b6 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:31, Info                  CSI    000002b7 [SR] Verify complete
2015-08-19 11:51:31, Info                  CSI    000002b8 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:31, Info                  CSI    000002b9 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:37, Info                  CSI    00000332 [SR] Verify complete
2015-08-19 11:51:37, Info                  CSI    00000333 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:37, Info                  CSI    00000334 [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:47, Info                  CSI    0000033b [SR] Verify complete
2015-08-19 11:51:47, Info                  CSI    0000033c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:47, Info                  CSI    0000033d [SR] Beginning Verify and Repair transaction
2015-08-19 11:51:55, Info                  CSI    0000034c [SR] Verify complete
2015-08-19 11:51:55, Info                  CSI    0000034d [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:51:55, Info                  CSI    0000034e [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:05, Info                  CSI    0000034f [SR] Verify complete
2015-08-19 11:52:05, Info                  CSI    00000350 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:05, Info                  CSI    00000351 [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:15, Info                  CSI    00000352 [SR] Verify complete
2015-08-19 11:52:15, Info                  CSI    00000353 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:15, Info                  CSI    00000354 [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:24, Info                  CSI    00000370 [SR] Verify complete
2015-08-19 11:52:24, Info                  CSI    00000371 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:24, Info                  CSI    00000372 [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:34, Info                  CSI    0000037f [SR] Verify complete
2015-08-19 11:52:34, Info                  CSI    00000380 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:34, Info                  CSI    00000381 [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:45, Info                  CSI    00000384 [SR] Verify complete
2015-08-19 11:52:45, Info                  CSI    00000385 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:45, Info                  CSI    00000386 [SR] Beginning Verify and Repair transaction
2015-08-19 11:52:50, Info                  CSI    00000387 [SR] Verify complete
2015-08-19 11:52:50, Info                  CSI    00000388 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:52:50, Info                  CSI    00000389 [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:01, Info                  CSI    00000395 [SR] Verify complete
2015-08-19 11:53:01, Info                  CSI    00000396 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:01, Info                  CSI    00000397 [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:16, Info                  CSI    000003b6 [SR] Verify complete
2015-08-19 11:53:16, Info                  CSI    000003b7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:16, Info                  CSI    000003b8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:22, Info                  CSI    000003bb [SR] Verify complete
2015-08-19 11:53:22, Info                  CSI    000003bc [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:22, Info                  CSI    000003bd [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:31, Info                  CSI    000003c6 [SR] Verify complete
2015-08-19 11:53:31, Info                  CSI    000003c7 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:31, Info                  CSI    000003c8 [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:43, Info                  CSI    000003e1 [SR] Verify complete
2015-08-19 11:53:43, Info                  CSI    000003e2 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:43, Info                  CSI    000003e3 [SR] Beginning Verify and Repair transaction
2015-08-19 11:53:55, Info                  CSI    00000410 [SR] Verify complete
2015-08-19 11:53:55, Info                  CSI    00000411 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:53:55, Info                  CSI    00000412 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:01, Info                  CSI    00000415 [SR] Verify complete
2015-08-19 11:54:01, Info                  CSI    00000416 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:01, Info                  CSI    00000417 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:08, Info                  CSI    00000420 [SR] Verify complete
2015-08-19 11:54:08, Info                  CSI    00000421 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:08, Info                  CSI    00000422 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:16, Info                  CSI    00000430 [SR] Verify complete
2015-08-19 11:54:16, Info                  CSI    00000431 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:16, Info                  CSI    00000432 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:22, Info                  CSI    00000443 [SR] Verify complete
2015-08-19 11:54:22, Info                  CSI    00000444 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:22, Info                  CSI    00000445 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:28, Info                  CSI    0000044b [SR] Verify complete
2015-08-19 11:54:29, Info                  CSI    0000044c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:29, Info                  CSI    0000044d [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:37, Info                  CSI    0000045b [SR] Verify complete
2015-08-19 11:54:37, Info                  CSI    0000045c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:37, Info                  CSI    0000045d [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:43, Info                  CSI    00000464 [SR] Verify complete
2015-08-19 11:54:43, Info                  CSI    00000465 [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:43, Info                  CSI    00000466 [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:51, Info                  CSI    0000046b [SR] Verify complete
2015-08-19 11:54:51, Info                  CSI    0000046c [SR] Verifying 100 (0x0000000000000064) components
2015-08-19 11:54:51, Info                  CSI    0000046d [SR] Beginning Verify and Repair transaction
2015-08-19 11:54:57, Info                  CSI    0000046f [SR] Verify complete

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 19, 2015, 09:25:16 am

I don't know why the desktop icon should have been empty, but the latest log will do fine.

The cmd that I gave you should just have produced the [SR] ones which are what it could and couldn't repair.

I've never come across Ownership warnings before - definitely a one for Shane to look at.

EDIT - That's strange - the second one with a 3 minute time difference doesn't show any errors at all ??

I'd still see what Shane makes of it, but see what dism /online /cleanup-image /restorehealth comes up with.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 19, 2015, 02:39:59 pm

It says 20%.

Errr......is ths all bad news?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 19, 2015, 03:33:37 pm

I'd mentioned this behaviour on another forum (I think) and was told that it did eventually complete.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Tone111 on August 19, 2015, 04:25:17 pm

Yes, I've had this same thing on my W 8.1 machine when running SFCFix, which I believe calls that dism command, and it sat on 20% for an absolute AGE :-\, but then to my surprise (just before I was about to kill it in task manager!) it did eventually finish and got through the other 80% considerably faster than the first 20! :)
Weird...

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 21, 2015, 05:58:12 am

Yoohoooooooooo!!  :cheesy: :cheesy: :cheesy:

He did finish it, just like you guys said! 100%, the repair was successful! The first time I waited at least an hour. This time it took somewhere up to 2.5 hours (I was away that long).

I will now do the sfc /scannow again.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 21, 2015, 07:06:15 am

It sure is a party day today!! No errors found!

Is it much effort to tell me how to make a full external system image? I can look it up but that always takes up so much time and I have put SO much time and energy in this laptop already. :S

So does this mean that my laptop is now 100% healthy? And that next time I re-install I can use that image and do a clean install of W 8.1 without the recovery key of Lenovo so I won't get all their crap?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 21, 2015, 07:49:41 am

Well, that took a bit of Googling. I found what looked like a create and restore site but it was giving tap F8 to get into the Advanced Boot options which doesn't work in Win 8.1

One for creating a system image - and as you'll have D: Data drive for your Recovery image, then include that when creating a system image.

It's a bit long winded but you've already checked that your system is okay, you could skip read that bit - but it can still be educational.

https://www.winhelp.us/system-image-backup-in-windows-8-1.html

And how to restore with a system image - http://www.eightforums.com/tutorials/2269-system-recovery-options-boot-windows-8-a.html

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 21, 2015, 09:59:22 am

Okay, I'll start studying that. Thanks a million!

I think I'll do this overhaul action with Windows Repair All In One and the scans and repairs you showed me with my desktop too.

One last remark (if I don't run into issues with the system image): could you just humour me, Boggin?  :smiley:  I'd really like to know if my laptop is in the best shape possible now. That would really make my day and  I can start using it with a BIG smile on my face and being SO proud of having achieved that myself with your help! I honestly find that TOO cool! :cheesy:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 21, 2015, 10:52:23 am

Oh, I have to add: I'm that enthusiastic because this is my first laptop! Only been on desktops before. And I look forward so much to going places with it!  :smiley:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 21, 2015, 02:00:42 pm

Well, the system file checks have come up okay and I assume it boots up okay and any programs you have installed work when you fire them up - then I'd say that you were good to go :)

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 21, 2015, 03:02:53 pm

Yeahhhhhhh, I'm happyyyyyy!!

Thanks again, all of you who helped me with this one. Your help means more to me than you know.  :smiley:

Bless you all.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 28, 2015, 11:41:39 am

Okay, that didn't go as smoothly as I hoped.

For starters, there was no option for a system image backup when I opened File History with Windows-key+Q. See clipping 1 (is clipping the English word?) It's in Dutch, but trust me. :) I found the system image backup option in Control Panel > File History and then in the lower left hand corner. The first backup I made looked good on the outside but turned out to contain 0 bytes. Did it again and it was okay, nearly 30 Gb. Did it again because the time mentioned with the top folder did not match with the last backup (apparently that doesn't change once it's made :S, we live and learn). Since then every backup turns out to be empty. Why did it go right one time and the other times did it have zero content? And how do I get it right??

Any ideas?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 28, 2015, 01:07:04 pm

I create my system images of my Win 7 on an external HDD but when I go into the files on the HDD and click on one of the images, that shows up as 0KB - but they do work.

I can only assume they are a short cut to something else - but don't know where.

When you create subsequent images onto an external HDD, it overwrites the previous one, so for info, when creating a new one, ensure everything is as it should be beforehand.

One way to check if an image has been created onto the external HDD is to right click on it and select Properties where under the General tab will show the disk size, space used and space remaining.

This obviously works better on a new HDD or one that you know the capacity of what should be there from other stored items.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 29, 2015, 06:16:12 am

Well, Boggin, I must say: your idea to check the disk size was brilliant! I wanted to delete the file, check the disk space and make the image backup again, but then I outsmarted myself! I moved the WindowsImageBackup folder to one of the internal harddrives, checked the disk space of the external HD and moved it back again. And YES! The disk size changed with 36 Gb!!!

But........I just now checked the properties of the file again. And now it does show the 36 Gb......

I now am completely convinced that Microsoft is out to get us all stark raving mad so they can take over the planet.  :evil:

Two last questions, if you please, Boggin.

-  Can I just copy this WindowsImageBackup folder to other external HDs for extra backup or do I have to make a new image backup on each HD individually?

-  Someone said it wasn't a good idea to partition the one internal HD in my laptop into three drives as it would worsen the internal HD's performance. Do you agree? I find it so very handy to put different files in different drives. :) But is it in any way detrimental to the laptop?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 29, 2015, 07:18:53 am

With you swapping that system image about, it would be worth checking to see if it still works - after creating a new one on another external HDD and I think I would prefer to create a new one rather than copy one from one place to another.

I've just left my images where they are and accepted they show as 0KB knowing that they work when needed.

Copying it onto your computer would probably have saved it as its actual size so that when you copied it back, it would now be showing as its actual size on the external HDD - but I don't know if that would impact on its attributes that it would still work as a system image.

Most laptops come with three partitions anyway - the hidden System, C:\ for the OS and programs and D:\ for the Recovery partition.

Some store stuff in the Recovery partition but I always preferred to leave that pristine but have since deleted the Recovery partition on both my laptops and merged with C: so there is just one big C:

I have seen where people have created additional partitions for this that and the other, but I like to keep things simple.

This article would debunk that partitions have an adverse effect on performance (haven't read it all), but I've deleted the Recovery partitions on both my laptops and merged into C: so I just have one large partition. http://www.pcworld.com/article/255224/how_to_partition_your_hard_drive_to_optimize_performance.html

After merging with C: and defragging, I ran Novabench and got a slightly better score, so not sure about the advantages of partitioning. https://novabench.com/

I do have Recovery disks should I need to factory reset, but store my system images on an external HDD and they are the first step to resolving a problem.

Rather than partitioning, why not use one of your external HDDs as the "partition" to store additional stuff on.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on August 30, 2015, 05:18:18 am

How can I see if the system image still works? Wouldn't that mean a re-install? :omg:

If I wanted to re-install again, I would like to install a clean version of 8.1 (I have the licence key). I hope that is possible. I assume this system image I just made still has these last Lenovo files I'm still not sure about whether I do need them and what they actually do.

I wondered: is this systemimagebackup exactly the same as the recovery key that Lenovo put in the laptop? I mean system-operation-wise.

This laptop has a button on the side to get the factory settings back if Windows cannot be started up anymore. For emergency cases, because you would get all the Lenovo stuff back as well, I guess. I'll keep the Lenovo recovery key file inside anyway, just to be safe. It is also only 0 Kb, haha, but I assume it's not that large a file. It's probably connected to that button on the side?

I removed the systemimagebackup I moved about and made a new imagebackup on the portable external HD (500 Gb) that I bought for my laptop and that will accompany me and my laptop on my future travels. (Yoohoo!!) I also made two extra backups on my other two external HDs that normally hang onto my desktop. And all images contain 0 kb. So I did it right. Hahaha. (Disk size increased, although differently on each HD: 29, 33 and 31 Gb. ?? I let that go. Must be right.)

Interesting article about improving performance of the partitions. I'm good now, though. The laptop's performance is good enough for me. At least it confirms that partitioning one internal HD is okay. I like things organized more than having a superhigh performance. :)

And yes, of course, I could use the external HD to put stuff on, but now I can take my laptop with me without the HD and still enjoy my music (the biggest partition E: and to me the most important  :cheesy:) AND I highly value making backups all the time if I have the external HD with me.

So, my dear Boggin, we can say the laptop is all done now and bright and shining inside!  :cheesy:

Thank you again for your time and effort. Cannot express my gratitude enough! I have one more question about the partitions in my desktop but I'll let you respond to this first.

Title: Re: Problems with Lenovo bloatware
Post by: Lady on August 30, 2015, 05:30:03 am

Quote from: Shane on July 28, 2015, 03:14:45 pm

Honestly it will take you longer to uninstall all that crap then it would to do a fresh install lol

Shane

Boy, was he right!!!  :cheesy:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on August 30, 2015, 08:20:13 am

I've seen where others have created system images on additional external HDDs as a belt and braces safeguard, but while I have two external HDDs I only save them on the one.

This system image that you have created after cleaning all of the bloat off, you may want to put that into a folder on one or more of the HDDs as that can be used to restore with instead of a factory reset with all of the bloat that you have just cleaned off and then create another one that will be overwritten with each subsequent new image.

Obviously anything thing that you've added since creating this image would be lost just as it would with a factory reset - but saving/storing your main personal stuff onto one of your HDDs will prevent that.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 04, 2015, 04:21:27 am

Four questions:

1.

Quote from: Boggin on August 30, 2015, 08:20:13 am

...you may want to put that into a folder on one or more of the HDDs.

When making the image backup I can't make my own folder and if I put it into a specific folder, say "SystemImageBackup basic" I would be moving the folder around again, which I learned was not advisable.

2. What kind of data added after the backup would be a reason to make a subsequent new image backup? Programs? Specific settings? I have no idea.

FYI Personal data (Word, notepad, new music files, pictures etc.) I always backup every day on at least two external HDs.

3. I still don't know if I'm able to make a clean installation of 8.1 with my licence key. No idea how I should do that but just to know if I can get 100% rid of anything Lenovo next time.

4. This Lenovo Service Engine: just to be absolutely sure, can I do their BIOS update for the Z41-70/Z51-70 (I have Z50-70) or can that be harmful if it doesn't apply to my laptop?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 04, 2015, 04:50:10 am

To do a clean install of any Windows version on an OEM machine requires a valid retail key as a Win 8.1 ISO would be different to your Lenovo OEM install.

However, this article will walk you through doing a repair install of Win 8.1 https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html but that wold only be necessary in extreme cases.

The idea behind putting your bloatware free system image into a folder is to protect it from subsequent images as it would be overwritten.

Normally with the files open on an external HDD you would right click in an open area and select New where you can then click on Folder, but you could also use DVDs to save the clean system image and keep those safe so that you can continue to overwrite with new images on the HDDs.

I think Lenovo will also afford you to create a set of Recovery Disks which will be a copy of your D: Recovery partition.

I don't have a lot on my laptops but I have a Wordpad doc where I keep my tools and as that is added to, I back that up onto a Flash drive.

Other than that, I only create a system image once a month on my Win 7 after the various Adobe and Windows Updates after running Disk Cleanup as an admin to remove any obsolete Windows Updates - a defrag and virus scan.

Generally speaking there is only a need to update the BIOS if you are having problems, but it may be best to contact Lenovo Support for clarification on that BIOS update, its benefits and if you need it.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 05, 2015, 04:55:56 am

Quote from: Boggin on September 04, 2015, 04:50:10 am

To do a clean install of any Windows version on an OEM machine requires a valid retail key as a Win 8.1 ISO would be different to your Lenovo OEM install.

However, this article will walk you through doing a repair install of Win 8.1 https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html but that wold only be necessary in extreme cases.

I kinda understand your first line but the article is way too difficult for me. Don't bother explaining further, Boggin. I'll let it be.

Quote from: Boggin on September 04, 2015, 04:50:10 am

The idea behind putting your bloatware free system image into a folder is to protect it from subsequent images as it would be overwritten.

Yes, I understood that perfectly, but you told me to not copy and paste the system image to another place. That's what confused me when you told me to put the basic image in its own folder. But I gather I can make its own folder for safekeeping. Okay. I will then.

Quote from: Boggin on September 04, 2015, 04:50:10 am

I think Lenovo will also afford you to create a set of Recovery Disks which will be a copy of your D: Recovery partition.

I have no clue what you mean by this. :S  Isn't the recovery partition on D: the same as Lenovo's Recovery Key or my system image backup?

Quote from: Boggin on September 04, 2015, 04:50:10 am

I don't have a lot on my laptops but I have a Wordpad doc where I keep my tools and as that is added to, I back that up onto a Flash drive.
Other than that, I only create a system image once a month on my Win 7 after the various Adobe and Windows Updates after running Disk Cleanup as an admin to remove any obsolete Windows Updates - a defrag and virus scan.

I'm afraid you totally lost me now. I'm SO confused that I don't understand any of it anymore. Can I just drop this and backup my personal files like I do all the time and just have one systembackupimage? I'm getting a very awful feeling of overload now.

Quote from: Boggin on September 04, 2015, 04:50:10 am

Generally speaking there is only a need to update the BIOS if you are having problems, but it may be best to contact Lenovo Support for clarification on that BIOS update, its benefits and if you need it.

Well, I tried several times to get in touch with Lenovo directly or find an answer online but their FAQs and automatic question systems don't mention the Search Engine AT ALL. So now I asked the question whether I have it or not on their (English) forum. I'll let you know.

Can you help me wrap this up in the easiest way possible, Boggin? It's getting too much for me now. Don't forget I'm a laywoman and not a native speaker of English. Although I have a Master's in Translation Studies with English as my major, with all this jargon and IT expertise i'm now in over my head. :S  And I was doing so well.....  :cry:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 05, 2015, 05:28:35 am

First of all, on my Toshiba Win 7 laptop in All Programs there's a Toshiba folder and in that is Recovery Media Creator'

Running this, Toshiba allows you to make one copy of Recovery Disks which is a copy of the D: Recovery Partition which you can factory reset the machine with should your system get so messed up or the HDD goes.

They provide this facility because they no longer supply install disks with the machine and yours may have the same provision.

When I'm talking about Tools -  have a couple of Wordpad Documents where I copy & paste useful URLs which have various fixes for computer problems and I back up these Wordpad docs onto an USB Flash drive stick.

Once a month in addition to Windows Updates, Adobe have been updating Flash Player and occasionally Shockwave and after they have been installed I'll do those preparations I've mentioned prior to creating my monthly system image.

When Disk Cleanup is run as an admin by right clicking on it, it will delete outdated Windows Updates and when run initially can clean out ~3GB.

This is only for Win 7 though.

As for the jargon etc. I think you have done very well in cleaning up your laptop :)

A tip - to get a smiley, type the : with ) or if you want a grin then use D instead of )

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 13, 2015, 03:35:49 am

I thought about this for a while. I believe what went wrong was that I thought a systembackupimage was saving the basic software, similar to what you get after a re-installation. (I don't know the jargon to put it differently. :S)

So in my SBI I just copied the C: and some system reserved part that were default anyway. Because I backup all my files I have on D: and E:.

You, Boggin, on the other hand, save a lot of your other data and current system settings in the SBI as well. That's where it went wrong. I got puzzled and had a bit of a meltdown. Mainly because I had been working on several pc issues for months and it hadn't been easy for me.

I thought about it but it still feels like too much for me to also keep a SBI up-to-date. With all the maintenance that I'm doing already (running various spyware/antivirus scans, cleaning the pc (I use Wise Disk Cleaner), trying to keep my privacy protected, solving problems with Windows that never seem to stop appearing :S, I think it's enough.

Re your tip about smileys: yes, I'm no IT expert but not a total nerd. :)) I assume that came about because you don't know this one:  :S  which I use a lot and means: "oops, that went wrong/feeling awkward or confused". At least, that's the kind of face I pull with these emotions, hahaha.

Among you guys I'm a novice, absolutely, but among my friends I'm the only one who takes care of her pc and laptop this meticulously. Some of them don't even back up their files or have an antivirus program!! Among them I'm the one-eyed queen, hahahaha. So I think I'm all set with just a basic SBI and my regular routine.

Don't you agree? :)

Oh, still no answer on the Lenovo forum. Repeated my question just now and put in the link that Samson gave me about the Lenovo Search Engine to perhaps wake some Lenovo users up.

Still immensely grateful for your help, Boggin. And for your patience going thru ALL these words of mine. :D

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 13, 2015, 04:54:22 am

I'm not sure if this is one of my off days, but what is a SBI :)

I'm not familiar with :s but that would only produce an emoticon if it was part of the forum's emoticons.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 13, 2015, 05:45:20 am

To avoid having to type it again and again: an SBI is a systemimagebackup. Not an official abbreviation, surely, but you COULD have guessed it. Off day it is, Boggin!  :cheesy: But you're right, next time I'll introduce it when I'm using an idiosyncratic abbreviation.

Yes, I know the :S is not part of the forum's emoticons, but that's not keeping me from using it.  :cheesy:

So now you know what an SBI is: do you agree with what I wrote?

Then we can close this and move on.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 13, 2015, 06:02:55 am

If it had been SIB perhaps, but I just type image if I've already referenced system image.

Are D: and E: external HDDs ?

A system image is a snapshot of what is on the computer at the time, but where you also have a Recovery partition, you can also include that in the image so that it is a full snapshot.

The downside of just relying on that is that when you restore with it, it's a all or nothing restore in that you cannot be selective in what you want to restore and backing up personal stuff separate is the way to go - as I do with my Wordpad Docs onto Flash drives.

It sounds as if you have everything under control, so I guess you could wrap this up.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 13, 2015, 06:19:14 am

Oh my goodness gracious me, I messed the letters up.................... :S

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 13, 2015, 06:31:34 am

Quote from: Lady on September 13, 2015, 06:19:14 am

Oh my goodness gracious me, I messed the letters up.................... :S

:D

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 13, 2015, 07:15:29 am

Talking about idiosyncrasies.............

But I could very well use my smiley there! Hahaha. Feeling VERY awkward indeed.

D: and E: are partitions of my internal HD where I keep my personal files and music files respectively. I have all these data backed up on my two external HDs F: and G: which are connected to my desktop pc permanently. Some smaller-sized important personal data like Word I also back-up sometimes on USB-sticks. And then I have my laptop now as well. Only when my house gets on fire I'm in trouble.  :cheesy:

Do you use flash drives for backup as they are more reliable than external HDs? And do you mean USB-sticks or external SSDs? Probably USB-sticks for Wordpad documents. I need a lot of backup space due to my large amount of audio, video and music files. SSDs are still too expensive.

I'd like to secure my external HDs (and USB-sticks) with a password. I read about it online, there are various programmes for it but what would you advise?

Or do you want me to start a new topic about this?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 13, 2015, 09:40:49 am

As I don't have anything sensitive or of import to anyone else and no one else has access to my bits and pieces, I've never considered password protecting either my laptops or external HDDs.

I did a Google on how do I password protect external hdd and a number of links came up, but nothing seems to be free - although StorageCrypt may suit your needs if you want a paid for program. https://7labs.heypub.com/tips-tricks/lock-external-hard-drive-with-password.html

Some external HDDs include encryption from what I've read, but any form of security lock on the HDDs you will be using for the system images could hamper Windows accessing them if you ever needed to restore with them.

Yes, I do mean USB sticks as the Wordpad docs aren't that large, although prior to factory resetting I will back up my Downloads and Documents folders onto a 16GB stick.

As D: and E: are internal partitions, I would expect those to be also listed to include when using Windows Create a system image to give you a full image of your computer.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 13, 2015, 11:39:23 am

Very good point there about access in case I need the SIB. (I did it right now, haha.) I forgot to mention it but data encryption programmes I ruled out earlier, as I read that those carry no small risk of permanently damaging one's data. I'll look into it later for my USB-sticks because recently I lost one with photos on it. Using one of these password programmes sounds alright.

Do you mean that you keep all your setup files that you download? For the sake of knowing which ones to download again? That might be a good idea. My solution to knowing my programmes is making a few screenshots of Programs and Features and saving those on my various backups.

See, now I get confused again with this SIB thing. If it's a snapshot of what's on the computer, doesn't it contain all the programmes that I downloaded? So why keep the download folder then? Does an SIB even copy all the tabs I have open in Firefox too e.g.?

Yes, D: and E: are listed in the SIB creating process but they only contain personal data, no system things (as far as I know). In fact, there's nothing more on them than there is on their backups on F: and G:. And they're large: 320 and 456 Gb resp. That's why I didn't include them in my SIB. It would only mean a double backup on the external HDs, wouldn't it?

No, there's one thing different. This file: 749dfcf3fecb51fcd07aca2b4b. I was told this was some malicious software removal tool by Microsoft and that I should leave it. Don't really know what to do with it, or does it do something on its own? What a stupid way of Microsoft to just install it like that. It just was there one day. Who of us non-IT people would know what that is. It actually looks like malware like this.  :rolleyes:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 13, 2015, 12:31:57 pm

There are some programs that don't actually install but run as a one off, so their Application stays in the Downloads folder, but there are others that have now been updated but I need to run the older version - the Downloads folder is also a handy place to keep trial versions of programs, so that once you have used them - you uninstall and then run it again from there which stops the clock on them.

Naughty I suppose, but why pay for a program that hardly gets used.

When you have valuable stuff like photos and music backed up, it's usually advocated that you have more than one back up should one of them fail.

External HDDs can fail or become corrupt just as internal ones can and I prefer to keep a separate back up of those folders should a system image fail, which has been known because of corruption.

I've only experienced one failure when I used DVDs and wanted to go back to the one before the last, but with an external HDD, you don't have that option.

Once you have created a system image you should restore with it to see if it works.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 14, 2015, 10:00:34 pm

Thank you, that was very informative.  :smiley:

Yes, I did that with Revo Uninstaller Pro until this friend of mine, the head of the tech dept. of my pc shop, told me to use the portable version which was freeware. But then I got into trouble as I didn't know that version only finds the 32-bits programs as you told me. So back to the naughty routine.  :smiley:

I thought we were finished, Boggin, but now I just found out I cannot make SIBs of my desktop pc. I'll make a new topic.

THANK YOU for all your help with this thread!!! <3

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 14, 2015, 10:39:08 pm

Second post:

To be clear: i'm now trying to make a SIB of my desktop pc.

I get an error message indicating there's something wrong with the I/O devices. See attachment. It's in Dutch, I'll translate:

-----------------------------------------------------------------

Making a system image backup

The backup failed.

One of the backup files cannot be made (0x8078002A)

Additional info:
The request could not be performed because of an I/O device error (0x8007045D)

-----------------------------------------------------------------


The backup failed for both my external HDDs with the same error message. I looked up the codes and different solutions are being given, like chkdsk for the external HDDs, but I don't understand. These HDDs are fairly new.

My intuitive feeling is that I first should do an overhaul of my desktop pc like I did with my laptop, remember? I wanted to do that after I cleaned my laptop as I have been feeling for a while that the desktop is not functioning properly anymore.  FYI: after I bought this desktop I had MAJOR problems with bluescreens and all kinds of nasty stuff. That's how I came here. Somebody told me to do a Windows Repair. And after a year of trying everything in the book on another forum and I was near a meltdown again as you can imagine, everything was solved after the Repair. I mean, Shane is my HERO now!

But I feel it's time to do some cleaning again. Would you mind helping me out again?

So the first step should be doing a Windows Repair All In One, right? I run all kinds of scans regularly, like MBAM and my BullGuard Antivirus programme, and ESET Online scanner, so there is no malware to be seen in miles around!! Or do you have any other suggestions to do first?

The Repair All In One should be run in Safe Mode if I remember correctly. I'm always scared of doing that, but I think I'll just pull myself through it again. :S

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 15, 2015, 01:58:21 am

What is the OS on the Desktop and have you been able to use these external HDDs on the Desktop before ?

Reading this article http://gadgets.itwriting.com/998-why-your-new-2tb-or-3tb-drive-will-not-work-with-windows-backup.html suggests it could be a compatibility issue as they are new HDDs, but run the command on each HDD as suggested in the article to see if this applies to your HDDs.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 16, 2015, 06:43:02 am

My desktop OS is Windows 7 Home Premium, Service Pack 1, 64 bits.

My external HDDs, both Seagate 2 Tb, were bought in August 2014 and February 2015 and are permanently connected to my desktop pc and have been performing flawlessly since they were attached. I use them daily for backing up files manually.

I read the article and ran the command for each HDD and they both have a 4K sector size, both physical and logical, so they're 4K native. I don't understand much of all kinds of related articles I read but I gather there is no solution if they're 4K native, only if they have a 4K logical and a 512-byte physical sector (Advanced Format). I looked on the Seagate site but they just say: use software that is 4K-aware.....which for the backup programmes is Windows 8 (my laptop has W8, indeed no problem with the SIB). I tried to make a SIB on my 500 Gb Seagate portable HD that I have for my laptop, but that didn't work either, although this HD has 4K physical sectors and a 512 logical sector (error code there was 0x80070015, searched on that code but nothing.) I guess I have to use the fix that is available for the Advanced Format HDDs, but I don't really want to use the small HDD for this SIB, it takes up more than 66 Gb.

Do you still follow me?  :cheesy:

So, I wasted a lot of hours reading difficult stuff and as far as I know now, this cannot be solved. Seagate points at Microsoft and Microsoft only made a fix for the Advanced Format HDDs. Western Digital seems to have made a fix for their 4K native HDDs......

I hope this is all correct what I'm stating. Well, I suppose I can live without the desktop SIB. :S  (See how often this smiley comes in handy, hahaha. The emoticon for "confused" looks the part, but it shouldn't be meaning confused, it's more like: oh, bummer.)  In case of a total crash, I just re-install the old-fashioned way.

Or can you come up with any ideas, Boggin?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 16, 2015, 07:43:35 am

Not if Seagate can't :D - compatibility is compatibility or lack of it.

Each system image for the same machine won't keep taking up 60 - 70GB each time as it just overwrites the previous one and would only grow by how much extra you had put on the machine.

I have system images for 4 laptops on a Seagate 500GB external and there's still ~240GB free - although there isn't a great deal on each machine.

I have a 1TB Seagate that works okay on a Win 7 laptop but I formatted that to NTFS before I used it, although from the article, only 2 and 3TB HDDs are afflicted with this problem.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 16, 2015, 11:04:22 am

BTW: I said it wrong: the portable HDD is 1 Tb, not 500 Gb. I forgot. :S  But it contains all backup data from the laptop, the biggest being my music file of over 400 Gb. That's why I was worried about all these Gbs of a SIB. But with 1 Tb it's no problem.

So it seemed the SIB on the portable HDD had failed. I got a hunch. [Hey, I'm a woman. :wink:] I removed the SIB that was on the portable (there were files missing and the volume of the HDD didn't increase after removing it, so it had failed). With the first attempt I had connected the HDD to my desktop via a USB hub and I have had trouble with transferring data via one of my hubs before, so I decided to disconnect one of my Big Boys HDDs which are both directly on a 3.0 USB port and I put the portable on that port. Closed all applications and tried again. It was done in no time and the volume decreased with 53 Gb. Only the MediaId file contains 4 Kb, the rest 0 Kb. So it worked! Not sure why it didn't work in the first place as it should have worked with the 512 sector. Didn't want to do any fix with my beautiful little blue HDD either.  :smiley: We solved another issue!! Hurray for us!

So..............big sigh...................let's continue, dear Boggin. This is where we left off. Is this the correct way to go about it? If so, please remind me how to do the safe mode again. I can look it up but my eyes are squared now. :S

Quote from: Lady on September 14, 2015, 10:39:08 pm

But I feel it's time to do some cleaning again. Would you mind helping me out again?

So the first step should be doing a Windows Repair All In One, right? I run all kinds of scans regularly, like MBAM and my BullGuard Antivirus programme, and ESET Online scanner, so there is no malware to be seen in miles around!! Or do you have any other suggestions to do first?

The Repair All In One should be run in Safe Mode if I remember correctly. I'm always scared of doing that, but I think I'll just pull myself through it again. :S

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 16, 2015, 12:34:36 pm

There's a button in WR to boot into Safe Mode for you but if you ever need to boot up into Safe Mode for trouble shooting purposes, this article will show ways in which do it. http://www.7tutorials.com/5-ways-boot-safe-mode-windows-8-windows-81

Personally I don't think you need to run WR on your new machine unless you think it isn't performing as it should.

Is the Hub's cable integral or is it replaceable ?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 16, 2015, 02:40:36 pm

Boggie,  :smiley:  you gotta stay with it! We're still working on the desktop pc now. With Windows 7. The laptop (W8.1) is all done! It's the scanning and repairing you showed me after I did WR on the laptop that gave me the idea to do the same with the desktop. Since I had so much trouble with it in the beginning. Maybe we can fix it to a tee now.  :cheesy: And after that, I'm ALLLLLLL done! And I'm going to enjoy the pc and the laptop for fun and regular things ONLY!!   :artist:

Oh, apart from the partition problem I'm having. [See my other topic.]

Oh yeah, I remember the button in WR now. I think I used it and it was easy. I'm just always scared to get it back into normal mode again but if I remember well, the pc returns to normal mode after reboot by itself, right?

The hub's USB cable is replaceable. Does that make it less reliable? I have two hubs. Both with replaceable cables, one with power chord.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 16, 2015, 04:33:38 pm

There have been a couple of instances posted on the forum where normal mode hasn't returned after the reboot, but that is easily resolved by going into msconfig (type that at Start and press enter) and under the Boot tab, uncheck any boxes under Safe Mode and then uncheck Safe Mode - Apply - OK and reboot.

A bad cable or cable connector can cause problems with Data transfer and changing or swapping over from the other one if compatible, could ID those as the cause of the previous SIB fail/corruption.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 17, 2015, 03:09:24 pm

Alright, no problem then.

I'm working on the partitions first because if that ends in a total crash, then I don't have to worry about a WR and scans/repairs etc.!

Hahahaha

Still laughing now.........

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 17, 2015, 03:47:24 pm

You have a point :D

Did you try swapping the cables over to see if a SIB would complete using one of the Hubs - or will that be for later ?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 17, 2015, 04:07:28 pm

Yeah, I just saw the one point!!! But now I have two!!! I don't know how I get those. Is that for working so arduously on my computers? :-)))

If I continue like this, I'll be joining you guys in answering questions, hahahahaha.

No, I'm not trying out the cables. Have so much on my plate right now. The partition thing is really BIG. Did you read my post about that? You're a Brit, you might have laughed out loud about the joke I just made there about my Partition Adventure!  :cheesy:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 17, 2015, 04:14:12 pm

Yes I did - and have you read my post on there ?

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 17, 2015, 04:25:16 pm

I just did.....

You guys are SO SWEET!!!

<3<3<3

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 21, 2015, 04:14:48 am

Boggin, I just now understood your trick of using Revo Pro over and over again for free. Could I in some way get the trial verson again without them knowing who I am? I threw the download away and cannot use Revo Pro without buying the licence. You mentioned using IOBit Uninstaller but when I clicked on the link you gave me earlier in this thread, MBAM blocked a malicious website (www.reimageplus.com). I thought MajorGeeks were clean? Can I still download the IOBit? I'd prefer to have Revo Pro though, 'cause I'm used to it and am very tired now of trying to find out how a new programme works. Hope you understand.

Then: I just checked to see if I got an answer on the Lenovo forum on the Search Engine. Nothing. But I clicked on a related article about Superfish and got a bit scared reading thru the comments. Apparently you can uninstall Superfish but it leaves hackable traces in the root certificates (?) and the registry. How do I know I still have those? If you read through the comments, people are pleading for clean OS disks. The last comment on page 2 by Fuzzilla is interesting but I'm not fully understanding all that is being said. Could you take a look and see if there's anything I should or could do to further secure my Lenovo laptop? And maybe get a clean recovery install set?? To refresh your memory: Superfish had been detected and removed by both MBAM and BullGuard the minute I opened up the laptop.  :smiley:

https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Removal-Instructions-for-VisualDiscovery-Superfish-application/ta-p/2029206/show-comments/true

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 21, 2015, 05:12:47 am

First of all, I've just downloaded IObit from http://www.majorgeeks.com/files/details/iobit_uninstaller.html and Norton 360 said it was safe without snagging any PuPs.

One thing to look out for though is when the blue IObit Run window comes up, is to uncheck the small box to the right of the Licence Agreement so that you don't inadvertently install Advanced System Care.

The following is an article for Superfish removal and the certificates. https://support.lenovo.com/us/en/product_security/superfish_uninstall

As the article says that some security programs may have changed the attributes of the auto installer such as by MBAM or Bullguard as in your case, I would recommend  following the manual steps.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 22, 2015, 08:01:03 am

I downloaded IOBit. With a new pc I'll use your trick with Revo Pro.  :smiley:

Your link to the Superfish uninstaller was wonderful! Thank you. Although I have Classic Shell installed and couldn't find the certificate manager, I found it thru typing certmgr.msc into the Search box (Googled that). I did the manual instruction. Superfish wasn't found as an application anymore, nor in the certificates for Windows, Firefox and Thunderbird. Good news!

Their last line was: "NOTE: There are benign additional files and registry entries which will remain after this procedure. Although they are harmless, the Superfish Removal Tool will remove them." So I did the automatic Removal Tool after all and, guess what, it did remove some registry entries! Yoohoo! I'm happy now.

My VERY last actions regarding the Lenovo crap will be these:

I want to remove two remaining Lenovo files in Program Files (x86) that are only visible in Explorer: the IMController and the MetricCollection one. But IOBit doesn't see them nor Programs and Features. Can I just remove them? See screenshot. "Bestandsmap" means "File directory". This is what I finally found out about them. Not very clear to me, but I think they can go.

MController: Optimize your day-to-day detailed planning using short-term simulations based on current order data.

policy.1.0.lenovo.metriccollectionsdk35.dll file information:

This file is part of unknown product process designed by unknown company, This file not necessary for your system, Keep this file running unless you suspected that this file cause problems to your system

Then the last two programs that I'm still not sure about whether they can or should go: the two driver packages. See screenshot.
They are not spotted by IOBit but are in Programs and Features, so I can delete them there. If you say so.  :cheesy:

I'm soooooo glad these are my last actions with the Lenovo crap! Afterwards I'll make a new SIB. And I'll try to get clean OS disks of W8.1 from Lenovo Netherlands. Who knows? We Dutch have a saying that goes: if you don't shoot, you'll always miss.  :cheesy:

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 22, 2015, 10:00:16 am

Firstly, is it you that I have to thank for the added Karma point ? :)

I think if they aren't causing any problems then I would be inclined to leave them.

If they are in msconfig either under Services or under the Startup tab where you can uncheck their boxes, they shouldn't be a problem - but check to see if anything appears to work differently after the reboot.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 25, 2015, 05:36:30 am

Both Lenovo programs are not in msconfig Services or Start-up. I did find in Services: Lenovo WiFiHotspot Service. Is that okay? Doesn't Windows have its own WiFi connection program? I don't know anything about WiFi and laptops. At home I use LAN-cables (much safer :D). If I'd take my laptop with me on an Expotition I wouldn't even know how to connect to a WiFi spot but I'll see about that when I get there. :) So I'll just leave those last Lenovo programs alone. Thanks, Boggin, for the advice! Do you realize we're REALLY done now with all the Lenovo crap and how much effort that took? Shame on them.  :evil:

I didn't give you that last karma point. If I remember correctly I gave you the karma point that made 21. :D

Now I'll defragment the discs (I use O&O Defrag Free) and do all the cleaning/virus scans/malware scans and the sfc /scannow again.

Is it okay if I send you a personal message? I'll explain why in it.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 25, 2015, 07:58:25 am

Yes, that would be okay.

My younger son and daughter in law have recently bought a Lenovo laptop but I think they've just left it as-is as they tend to use an iPad for general stuff and my daughter in law uses the laptop for her solicitor's work.

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Lady on September 25, 2015, 11:47:24 am

Well, to each his own! :smiley:

I know a lot of people, and I don't mean to include your son and daughter in law, don't feel like putting in all this effort and don't really care about their privacy issues or the risk of getting infected and so on. But Superfish and the Lenovo Search Engine were seriously bad, so it might be a good thing if they checked and removed at least those.

And, don't forget, if I had a father like you standing right behind me, I'd be REALLY laid-back about my computers!! Hahahaha

Title: Re: (Solved) Problems with Lenovo bloatware
Post by: Boggin on September 25, 2015, 01:42:17 pm

They were aware of Superfish and I believe they've gotten rid of it but have probably just left the bloat on.

As long as it works then they are quite happy :)