Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win 7 suddenly asked for sign in PW Now many programs not working


  • This topic is locked This topic is locked
12 replies to this topic

#1 AhhhLeah

AhhhLeah

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 23 February 2018 - 01:20 PM

Windows 7 suddenly asked for PW to sign in even though I did not change that setting.  Didn't remember the PW so went in through back door and disabled PW again.  Found some programs no longer work and settings of other programs have been changed.  Am told I don't have permission to do certain things even though I am the Admin.  Two user ID's vanished from the sign on screen.  Avast and Malwarebytes seemed to be locked.  Prob other issues I haven't yet run across.
 
Tried repeatedly to do a system restore in and out of safe mode.  Each time was told it did not complete, a file was missing or my antivirus was running.  Could confirm Avast and the firewall were disabled but still couldn't get into Malwarebytes so finally ended up uninstalling it.  Again was told the system restore did not work for the same reason but nothing was running. Now Malwarebytes won't download at all.
 
Unable to confirm I have a virus.  Don't know what's going on.  Thank you in advance.
 
 
Mod Edit:  Removed FRST data from Win 7 topic - Hamluis.

Edited by hamluis, 24 February 2018 - 06:44 AM.


BC AdBot (Login to Remove)

 


#2 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:07:28 AM

Posted 23 February 2018 - 05:39 PM

JsngtRvr of the malware response team says this is a Windows problem -

 

Error: (02/23/2018 11:51:20 AM) (Source: Microsoft-Windows-User Profiles Service) (EventID: 1542) (User: NT AUTHORITY)
Description: Windows cannot load classes registry file.
DETAIL - Unspecified error

 

I am taking him at his opinion.

 

Chris Cosgrove


Edited by Chris Cosgrove, 23 February 2018 - 06:14 PM.


#3 AhhhLeah

AhhhLeah
  • Topic Starter

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 23 February 2018 - 08:24 PM

Thank you so much for your response!  Now, can you dumb that down for me?  Contact Microsoft?  I just opened my Microsoft updater and see there are 14 updates waiting to be updated, some dating back to 2012.  What in the heck?  Those weren't there before all this started yesterday.



#4 JSntgRvr

JSntgRvr

    Master Surgeon General


  • Malware Response Team
  • 11,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:02:28 AM

Posted 23 February 2018 - 10:56 PM

It is a problem in the registry. Also there are signs that you ran CHKDSK. Was there any findings on that scan

  1. Click Start.

  2. Type cmd, and then press CTRL+SHIFT+ENTER to open elevated command prompt(I.e. Command prompt with admin rights).

  3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  4. Type or copy paste the below command lines into it one at a time and press Enter:

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

sfc /scannow

Exit

 

Let us know if the issue persists.


No request for help throughout private messaging will be attended.

If I have helped you, consider making a donation to help me continue the fight against Malware!
btn_donate_SM.gif


#5 ranchhand_

ranchhand_

  • Members
  • 1,643 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Midwest
  • Local time:12:28 AM

Posted 23 February 2018 - 11:16 PM

I didn't have time to dig deeply into your post, but you have Searchscopes on your computer. This is adware. Judging from your post, I suggest you check in at the "Am I Infected?" forum. Sounds like a virus to me.


Help Requests: If there is no reply after 3 days I remove the thread from my answer list. For further help PM me.


#6 AhhhLeah

AhhhLeah
  • Topic Starter

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 24 February 2018 - 01:19 AM

Also there are signs that you ran CHKDSK. Was there any findings on that scan

 

No findings

 

I picked a couple of comments to share with you below.  I couldn't copy and paste so I didn't get all the notes.

 

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

 

Error:  07

The restore health option is not recognized in this context

 

sfc /scannow

 

Windows Resource Protection found corrupt files and successfully repaired them. 

 

Exit

 

Let us know if the issue persists.

 

Thank you for your help.  Will post again if I continue to see probs.


I didn't have time to dig deeply into your post, but you have Searchscopes on your computer. This is adware. Judging from your post, I suggest you check in at the "Am I Infected?" forum. Sounds like a virus to me.

 

Will do.  Thank you for your time.



#7 pcpunk

pcpunk

  • Members
  • 5,773 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:02:28 AM

Posted 24 February 2018 - 09:34 AM

DISM is not to be run on Windows 7 from what I understand so that's why it failed.  Looks like some things were fixed how is it running now?


sBCcBvM.png

Created by Mike_Walsh

 

KDE, Ruler of all Distro's

eps2.4_m4ster-s1ave.aes_pcpunk_leavemehere

 


#8 JSntgRvr

JSntgRvr

    Master Surgeon General


  • Malware Response Team
  • 11,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:02:28 AM

Posted 24 February 2018 - 10:01 AM

  • Copy the entire contents of the Quote Box below to Notepad.
  • Name the file as Runme.bat
  • Change the Save as Type to All Files
  • and Save it on the desktop
  • Once saved, right click on the RunMe.bat file and Run as Administrator.
  • Post the sfcdetails.txt that will be produced on your desktop.

 

 

@Echo OFF
cd /d %~dp0
Color 1f
Echo Please wait...........
Type C:\Windows\Logs\DISM\dism.log >"%userprofile%\Desktop\sfcdetails.txt"
Echo . >>"%userprofile%\Desktop\sfcdetails.txt"
Echo . >>"%userprofile%\Desktop\sfcdetails.txt"
Echo . >>"%userprofile%\Desktop\sfcdetails.txt"
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >>"%userprofile%\Desktop\sfcdetails.txt"
Start "%userprofile%\Desktop\sfcdetails.txt"
Exit

 

Two cents:

 

DISM is not to be run on Windows 7 from what I understand so that's why it failed.  Looks like some things were fixed how is it running now?

 

 

While "DISM Supported Platforms" also provides this: "Deployment Image Servicing and Management (DISM) works on Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server® 2012, Windows 7, and Windows Server 2008 R2 images. However, the full functionality is available only when you are servicing a Windows 8.1 or Windows Server 2012 R2 image. This is because the files and resources required to service any Windows image are located in the image, not on the technician computer. DISM will detect and use the resources available in the target image to update the image.


No request for help throughout private messaging will be attended.

If I have helped you, consider making a donation to help me continue the fight against Malware!
btn_donate_SM.gif


#9 AhhhLeah

AhhhLeah
  • Topic Starter

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 24 February 2018 - 11:39 AM

Very slowly.  I'll update you after I complete your next task.  Thank you again.



#10 AhhhLeah

AhhhLeah
  • Topic Starter

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 24 February 2018 - 11:52 AM

Part 1 ---

 

 

2018-02-23 23:15:56, Info                  DISM   PID=8552 Scratch directory set to 'C:\Users\Gail\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-02-23 23:15:56, Info                  DISM   PID=8552 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadImageSession
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Manager: PID=8552 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM.EXE:
2018-02-23 23:15:56, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-02-23 23:15:56, Info                  DISM   DISM.EXE:
2018-02-23 23:15:56, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-02-23 23:15:56, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Cleanup-image /Scanhealth
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:15:56, Info                  DISM   DISM Provider Store: PID=8552 Loading Provider from location C:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:15:57, Info                  DISM   DISM Provider Store: PID=8552 Connecting to the provider located at C:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:15:57, Info                  DISM   DISM Provider Store: PID=8552 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:15:57, Info                  DISM   DISM Provider Store: PID=8552 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:01, Info                  DISM   DISM Manager: PID=8552 Successfully loaded the ImageSession at "C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F" - CDISMManager::LoadImageSession
2018-02-23 23:16:01, Info                  DISM   DISM Image Session: PID=8820 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-02-23 23:16:01, Info                  DISM   DISM Provider Store: PID=8820 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:16:01, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:01, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:01, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:01, Info                  DISM   DISM OS Provider: PID=8820 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:16:01, Info                  DISM   DISM OS Provider: PID=8820 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Warning               DISM   DISM Provider Store: PID=8820 Failed to Load the provider: C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Manager: PID=8552 Image session successfully loaded from the temporary location: C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F - CDISMManager::CreateImageSession
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:16:02, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:16:02, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.23505, Image architecture=amd64
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:02, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:03, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:03, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:03, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:16:03, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:16:04, Info                  DISM   DISM Package Manager: PID=8820 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-02-23 23:16:04, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:16:04, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:16:04, Info                  DISM   DISM Package Manager: PID=8820 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-02-23 23:16:18, Info                  DISM   DISM Package Manager: PID=8820 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:18, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:16:19, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:16:19, Info                  DISM   DISM OS Provider: PID=8820 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-02-23 23:16:19, Info                  DISM   DISM Driver Manager: PID=8820 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:19, Info                  DISM   DISM Provider Store: PID=8820 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\F55422A2-9CCC-4DB9-B01A-F5828271088F\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-02-23 23:16:20, Info                  DISM   DISM Transmog Provider: PID=8820 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-02-23 23:16:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Provider Store: PID=8820 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:16:20, Info                  DISM   DISM Package Manager: PID=8820 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-02-23 23:16:20, Info                  DISM   DISM Package Manager: PID=8820 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:16:20, Info                  DISM   DISM Package Manager: PID=8820 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:16:20, Info                  DISM   DISM Package Manager: PID=8820 Start running scanhealth. - CDISMPackageManager::ScanHealth
2018-02-23 23:18:22, Info                  DISM   DISM Image Session: PID=8820 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Package Manager: PID=8820 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:18:22, Info                  DISM   DISM Provider Store: PID=8820 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:20:02, Info                  DISM   PID=8924 Scratch directory set to 'C:\Users\Gail\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-02-23 23:20:02, Info                  DISM   PID=8924 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadImageSession
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM Manager: PID=8924 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:20:02, Info                  DISM   DISM.EXE:
2018-02-23 23:20:02, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-02-23 23:20:02, Info                  DISM   DISM.EXE:
2018-02-23 23:20:02, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-02-23 23:20:02, Error                 DISM   DISM.EXE: Failed validating command line: DISM.exe  /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth sfc /scannow Exit
2018-02-23 23:20:02, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-02-23 23:20:02, Info                  DISM   DISM.EXE:
2018-02-23 23:20:02, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2018-02-23 23:20:02, Info                  DISM   DISM.EXE:
2018-02-23 23:20:02, Info                  DISM   DISM Image Session: PID=8924 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:20:02, Info                  DISM   DISM Provider Store: PID=8924 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:21:24, Info                  DISM   PID=8300 Scratch directory set to 'C:\Users\Gail\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-02-23 23:21:24, Info                  DISM   PID=8300 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadImageSession
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Manager: PID=8300 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM.EXE:
2018-02-23 23:21:24, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-02-23 23:21:24, Info                  DISM   DISM.EXE:
2018-02-23 23:21:24, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-02-23 23:21:24, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Cleanup-image /Scanhealth
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Loading Provider from location C:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Connecting to the provider located at C:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:21:24, Info                  DISM   DISM Provider Store: PID=8300 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Manager: PID=8300 Successfully loaded the ImageSession at "C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C" - CDISMManager::LoadImageSession
2018-02-23 23:21:26, Info                  DISM   DISM Image Session: PID=7076 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM OS Provider: PID=7076 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM OS Provider: PID=7076 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Warning               DISM   DISM Provider Store: PID=7076 Failed to Load the provider: C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Manager: PID=8300 Image session successfully loaded from the temporary location: C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C - CDISMManager::CreateImageSession
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:21:26, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.23505, Image architecture=amd64
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:21:26, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-02-23 23:21:26, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:21:26, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:21:26, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:21:26, Info                  DISM   DISM OS Provider: PID=7076 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-02-23 23:21:26, Info                  DISM   DISM Driver Manager: PID=7076 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\5FE729FF-2CDF-4BE1-96F1-362BBAB6AA6C\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-02-23 23:21:26, Info                  DISM   DISM Transmog Provider: PID=7076 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-02-23 23:21:26, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Provider Store: PID=7076 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:21:26, Info                  DISM   DISM Package Manager: PID=7076 Start running scanhealth. - CDISMPackageManager::ScanHealth
2018-02-23 23:22:55, Info                  DISM   DISM Image Session: PID=7076 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Package Manager: PID=7076 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:22:55, Info                  DISM   DISM Provider Store: PID=7076 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:24:15, Info                  DISM   PID=8852 Scratch directory set to 'C:\Users\Gail\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-02-23 23:24:15, Info                  DISM   PID=8852 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadImageSession
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Manager: PID=8852 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM.EXE:
2018-02-23 23:24:15, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-02-23 23:24:15, Info                  DISM   DISM.EXE:
2018-02-23 23:24:15, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-02-23 23:24:15, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Cleanup-image /Scanhealth
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Loading Provider from location C:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Connecting to the provider located at C:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:24:15, Info                  DISM   DISM Provider Store: PID=8852 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Manager: PID=8852 Successfully loaded the ImageSession at "C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB" - CDISMManager::LoadImageSession
2018-02-23 23:24:16, Info                  DISM   DISM Image Session: PID=3024 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM OS Provider: PID=3024 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM OS Provider: PID=3024 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Warning               DISM   DISM Provider Store: PID=3024 Failed to Load the provider: C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Manager: PID=8852 Image session successfully loaded from the temporary location: C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB - CDISMManager::CreateImageSession
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:24:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.23505, Image architecture=amd64
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:24:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-02-23 23:24:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:24:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:24:16, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:24:16, Info                  DISM   DISM OS Provider: PID=3024 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-02-23 23:24:16, Info                  DISM   DISM Driver Manager: PID=3024 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\19D01EA8-A706-4365-AAB1-FCB0FB92CFAB\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-02-23 23:24:16, Info                  DISM   DISM Transmog Provider: PID=3024 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-02-23 23:24:16, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Provider Store: PID=3024 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:24:16, Info                  DISM   DISM Package Manager: PID=3024 Start running scanhealth. - CDISMPackageManager::ScanHealth
2018-02-23 23:25:03, Info                  DISM   DISM Image Session: PID=3024 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Package Manager: PID=3024 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:03, Info                  DISM   DISM Provider Store: PID=3024 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:56, Info                  DISM   PID=6664 Scratch directory set to 'C:\Users\Gail\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-02-23 23:25:56, Info                  DISM   PID=6664 Successfully loaded the ImageSession at "C:\windows\System32\Dism" - CDISMManager::LoadImageSession
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Manager: PID=6664 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM.EXE:
2018-02-23 23:25:56, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-02-23 23:25:56, Info                  DISM   DISM.EXE:
2018-02-23 23:25:56, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-02-23 23:25:56, Info                  DISM   DISM.EXE: Executing command line: DISM.exe  /Online /Cleanup-image /Restorehealth
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Loading Provider from location C:\windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Connecting to the provider located at C:\windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-02-23 23:25:56, Info                  DISM   DISM Provider Store: PID=6664 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Manager: PID=6664 Successfully loaded the ImageSession at "C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934" - CDISMManager::LoadImageSession
2018-02-23 23:25:57, Info                  DISM   DISM Image Session: PID=7340 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM OS Provider: PID=7340 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM OS Provider: PID=7340 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Warning               DISM   DISM Provider Store: PID=7340 Failed to Load the provider: C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Manager: PID=6664 Image session successfully loaded from the temporary location: C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934 - CDISMManager::CreateImageSession
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:25:57, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.23505, Image architecture=amd64
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:25:57, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-02-23 23:25:57, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:25:57, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-02-23 23:25:57, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\pkgmgr.exe" : got STATUS_SUCCESS
2018-02-23 23:25:57, Info                  DISM   DISM OS Provider: PID=7340 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-02-23 23:25:57, Info                  DISM   DISM Driver Manager: PID=7340 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Loading Provider from location C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Connecting to the provider located at C:\Users\Gail\AppData\Local\Temp\85B28303-669C-4AB4-B0C9-14F7ECDE4934\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
 


2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-02-23 23:25:57, Info                  DISM   DISM Transmog Provider: PID=7340 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 The option(restorehealth) is not recognized in this context. - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-02-23 23:25:57, Info                  DISM   DISM Image Session: PID=7340 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Package Manager: PID=7340 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=7340 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-02-23 23:25:57, Info                  DISM   DISM.EXE:
2018-02-23 23:25:57, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2018-02-23 23:25:57, Info                  DISM   DISM.EXE:
2018-02-23 23:25:57, Info                  DISM   DISM Image Session: PID=6664 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=6664 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=6664 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-02-23 23:25:57, Info                  DISM   DISM Provider Store: PID=6664 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
.
.
.
2018-02-23 23:27:06, Info                  CSI    00000009 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:06, Info                  CSI    0000000a [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:08, Info                  CSI    0000000c [SR] Verify complete
2018-02-23 23:27:09, Info                  CSI    0000000d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:09, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:11, Info                  CSI    00000010 [SR] Verify complete
2018-02-23 23:27:13, Info                  CSI    00000011 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:13, Info                  CSI    00000012 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:15, Info                  CSI    00000014 [SR] Verify complete
2018-02-23 23:27:17, Info                  CSI    00000015 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:17, Info                  CSI    00000016 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:19, Info                  CSI    00000018 [SR] Verify complete
2018-02-23 23:27:20, Info                  CSI    00000019 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:20, Info                  CSI    0000001a [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:22, Info                  CSI    0000001c [SR] Verify complete
2018-02-23 23:27:24, Info                  CSI    0000001d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:24, Info                  CSI    0000001e [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:26, Info                  CSI    00000020 [SR] Verify complete
2018-02-23 23:27:27, Info                  CSI    00000021 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:27, Info                  CSI    00000022 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:29, Info                  CSI    00000024 [SR] Verify complete
2018-02-23 23:27:31, Info                  CSI    00000025 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:31, Info                  CSI    00000026 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:33, Info                  CSI    00000028 [SR] Verify complete
2018-02-23 23:27:35, Info                  CSI    00000029 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:35, Info                  CSI    0000002a [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:36, Info                  CSI    0000002c [SR] Verify complete
2018-02-23 23:27:38, Info                  CSI    0000002d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:38, Info                  CSI    0000002e [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:40, Info                  CSI    00000030 [SR] Verify complete
2018-02-23 23:27:41, Info                  CSI    00000031 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:41, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:43, Info                  CSI    00000034 [SR] Verify complete
2018-02-23 23:27:44, Info                  CSI    00000035 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:44, Info                  CSI    00000036 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:46, Info                  CSI    00000038 [SR] Verify complete
2018-02-23 23:27:48, Info                  CSI    00000039 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:48, Info                  CSI    0000003a [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:50, Info                  CSI    0000003c [SR] Verify complete
2018-02-23 23:27:52, Info                  CSI    0000003d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:52, Info                  CSI    0000003e [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:54, Info                  CSI    00000040 [SR] Verify complete
2018-02-23 23:27:56, Info                  CSI    00000041 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:56, Info                  CSI    00000042 [SR] Beginning Verify and Repair transaction
2018-02-23 23:27:57, Info                  CSI    00000044 [SR] Verify complete
2018-02-23 23:27:59, Info                  CSI    00000045 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:27:59, Info                  CSI    00000046 [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:01, Info                  CSI    00000048 [SR] Verify complete
2018-02-23 23:28:02, Info                  CSI    00000049 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:02, Info                  CSI    0000004a [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:04, Info                  CSI    0000004c [SR] Verify complete
2018-02-23 23:28:06, Info                  CSI    0000004d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:06, Info                  CSI    0000004e [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:08, Info                  CSI    00000050 [SR] Verify complete
2018-02-23 23:28:09, Info                  CSI    00000051 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:09, Info                  CSI    00000052 [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:12, Info                  CSI    00000054 [SR] Verify complete
2018-02-23 23:28:13, Info                  CSI    00000055 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:13, Info                  CSI    00000056 [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:19, Info                  CSI    00000058 [SR] Verify complete
2018-02-23 23:28:21, Info                  CSI    00000059 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:21, Info                  CSI    0000005a [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:23, Info                  CSI    0000005c [SR] Verify complete
2018-02-23 23:28:25, Info                  CSI    0000005d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:25, Info                  CSI    0000005e [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:31, Info                  CSI    00000060 [SR] Verify complete
2018-02-23 23:28:35, Info                  CSI    00000061 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:35, Info                  CSI    00000062 [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:41, Info                  CSI    00000064 [SR] Verify complete
2018-02-23 23:28:46, Info                  CSI    00000065 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:28:46, Info                  CSI    00000066 [SR] Beginning Verify and Repair transaction
2018-02-23 23:28:56, Info                  CSI    00000068 [SR] Verify complete
2018-02-23 23:29:00, Info                  CSI    00000069 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:00, Info                  CSI    0000006a [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:07, Info                  CSI    0000006c [SR] Verify complete
2018-02-23 23:29:09, Info                  CSI    0000006d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:09, Info                  CSI    0000006e [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:12, Info                  CSI    00000070 [SR] Verify complete
2018-02-23 23:29:14, Info                  CSI    00000071 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:14, Info                  CSI    00000072 [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:15, Info                  CSI    00000074 [SR] Verify complete
2018-02-23 23:29:17, Info                  CSI    00000075 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:17, Info                  CSI    00000076 [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:19, Info                  CSI    00000078 [SR] Verify complete
2018-02-23 23:29:20, Info                  CSI    00000079 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:20, Info                  CSI    0000007a [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:24, Info                  CSI    0000007c [SR] Verify complete
2018-02-23 23:29:25, Info                  CSI    0000007d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:25, Info                  CSI    0000007e [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:32, Info                  CSI    00000080 [SR] Verify complete
2018-02-23 23:29:32, Info                  CSI    00000081 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:32, Info                  CSI    00000082 [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:38, Info                  CSI    00000084 [SR] Verify complete
2018-02-23 23:29:38, Info                  CSI    00000085 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:38, Info                  CSI    00000086 [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:42, Info                  CSI    00000088 [SR] Verify complete
2018-02-23 23:29:43, Info                  CSI    00000089 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:43, Info                  CSI    0000008a [SR] Beginning Verify and Repair transaction
2018-02-23 23:29:54, Info                  CSI    0000008d [SR] Verify complete
2018-02-23 23:29:55, Info                  CSI    0000008e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:29:55, Info                  CSI    0000008f [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:06, Info                  CSI    00000093 [SR] Verify complete
2018-02-23 23:30:07, Info                  CSI    00000094 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:07, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:14, Info                  CSI    00000098 [SR] Verify complete
2018-02-23 23:30:15, Info                  CSI    00000099 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:15, Info                  CSI    0000009a [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:23, Info                  CSI    0000009d [SR] Verify complete
2018-02-23 23:30:24, Info                  CSI    0000009e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:24, Info                  CSI    0000009f [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:33, Info                  CSI    000000a1 [SR] Verify complete
2018-02-23 23:30:34, Info                  CSI    000000a2 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:34, Info                  CSI    000000a3 [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:47, Info                  CSI    000000c8 [SR] Verify complete
2018-02-23 23:30:48, Info                  CSI    000000c9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:48, Info                  CSI    000000ca [SR] Beginning Verify and Repair transaction
2018-02-23 23:30:57, Info                  CSI    000000cc [SR] Verify complete
2018-02-23 23:30:58, Info                  CSI    000000cd [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:30:58, Info                  CSI    000000ce [SR] Beginning Verify and Repair transaction
2018-02-23 23:31:06, Info                  CSI    000000d0 [SR] Verify complete
2018-02-23 23:31:07, Info                  CSI    000000d1 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:31:07, Info                  CSI    000000d2 [SR] Beginning Verify and Repair transaction
2018-02-23 23:31:14, Info                  CSI    000000d4 [SR] Verify complete
2018-02-23 23:31:15, Info                  CSI    000000d5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:31:15, Info                  CSI    000000d6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:31:25, Info                  CSI    000000d8 [SR] Verify complete
2018-02-23 23:31:26, Info                  CSI    000000d9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:31:26, Info                  CSI    000000da [SR] Beginning Verify and Repair transaction
2018-02-23 23:31:36, Info                  CSI    000000dc [SR] Verify complete
2018-02-23 23:31:37, Info                  CSI    000000dd [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:31:37, Info                  CSI    000000de [SR] Beginning Verify and Repair transaction
2018-02-23 23:32:15, Info                  CSI    000000e2 [SR] Verify complete
2018-02-23 23:32:16, Info                  CSI    000000e3 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:32:16, Info                  CSI    000000e4 [SR] Beginning Verify and Repair transaction
2018-02-23 23:32:31, Info                  CSI    00000105 [SR] Verify complete
2018-02-23 23:32:32, Info                  CSI    00000106 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:32:32, Info                  CSI    00000107 [SR] Beginning Verify and Repair transaction
2018-02-23 23:32:52, Info                  CSI    00000109 [SR] Verify complete
2018-02-23 23:32:53, Info                  CSI    0000010a [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:32:53, Info                  CSI    0000010b [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:15, Info                  CSI    0000010f [SR] Verify complete
2018-02-23 23:33:15, Info                  CSI    00000110 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:15, Info                  CSI    00000111 [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:20, Info                  CSI    00000113 [SR] Verify complete
2018-02-23 23:33:21, Info                  CSI    00000114 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:21, Info                  CSI    00000115 [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:24, Info                  CSI    00000117 [SR] Verify complete
2018-02-23 23:33:24, Info                  CSI    00000118 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:24, Info                  CSI    00000119 [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:28, Info                  CSI    0000011b [SR] Verify complete
2018-02-23 23:33:29, Info                  CSI    0000011c [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:29, Info                  CSI    0000011d [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:46, Info                  CSI    00000130 [SR] Verify complete
2018-02-23 23:33:46, Info                  CSI    00000131 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:46, Info                  CSI    00000132 [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:51, Info                  CSI    00000134 [SR] Verify complete
2018-02-23 23:33:52, Info                  CSI    00000135 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:52, Info                  CSI    00000136 [SR] Beginning Verify and Repair transaction
2018-02-23 23:33:55, Info                  CSI    00000138 [SR] Verify complete
2018-02-23 23:33:56, Info                  CSI    00000139 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:33:56, Info                  CSI    0000013a [SR] Beginning Verify and Repair transaction
2018-02-23 23:34:03, Info                  CSI    0000013c [SR] Verify complete
2018-02-23 23:34:04, Info                  CSI    0000013d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:34:04, Info                  CSI    0000013e [SR] Beginning Verify and Repair transaction
2018-02-23 23:34:12, Info                  CSI    00000140 [SR] Verify complete
2018-02-23 23:34:14, Info                  CSI    00000141 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:34:14, Info                  CSI    00000142 [SR] Beginning Verify and Repair transaction
2018-02-23 23:35:00, Info                  CSI    00000146 [SR] Verify complete
2018-02-23 23:35:01, Info                  CSI    00000147 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:35:01, Info                  CSI    00000148 [SR] Beginning Verify and Repair transaction
2018-02-23 23:35:09, Info                  CSI    0000014a [SR] Verify complete
2018-02-23 23:35:09, Info                  CSI    0000014b [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:35:09, Info                  CSI    0000014c [SR] Beginning Verify and Repair transaction
2018-02-23 23:35:12, Info                  CSI    0000014e [SR] Verify complete
2018-02-23 23:35:13, Info                  CSI    0000014f [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:35:13, Info                  CSI    00000150 [SR] Beginning Verify and Repair transaction
2018-02-23 23:35:36, Info                  CSI    00000152 [SR] Verify complete
2018-02-23 23:35:37, Info                  CSI    00000153 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:35:37, Info                  CSI    00000154 [SR] Beginning Verify and Repair transaction
2018-02-23 23:35:55, Info                  CSI    00000156 [SR] Verify complete
2018-02-23 23:36:00, Info                  CSI    00000157 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:36:00, Info                  CSI    00000158 [SR] Beginning Verify and Repair transaction
2018-02-23 23:36:54, Info                  CSI    0000015a [SR] Verify complete
2018-02-23 23:36:57, Info                  CSI    0000015b [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:36:57, Info                  CSI    0000015c [SR] Beginning Verify and Repair transaction
2018-02-23 23:38:07, Info                  CSI    0000016b [SR] Verify complete
2018-02-23 23:38:09, Info                  CSI    0000016c [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:38:09, Info                  CSI    0000016d [SR] Beginning Verify and Repair transaction
2018-02-23 23:38:49, Info                  CSI    00000178 [SR] Verify complete
2018-02-23 23:38:53, Info                  CSI    00000179 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:38:53, Info                  CSI    0000017a [SR] Beginning Verify and Repair transaction
2018-02-23 23:43:34, Info                  CSI    0000017c [SR] Verify complete
2018-02-23 23:43:35, Info                  CSI    0000017d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:43:35, Info                  CSI    0000017e [SR] Beginning Verify and Repair transaction
2018-02-23 23:43:50, Info                  CSI    00000180 [SR] Verify complete
2018-02-23 23:43:52, Info                  CSI    00000181 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:43:52, Info                  CSI    00000182 [SR] Beginning Verify and Repair transaction
2018-02-23 23:44:25, Info                  CSI    00000185 [SR] Verify complete
2018-02-23 23:44:26, Info                  CSI    00000186 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:44:26, Info                  CSI    00000187 [SR] Beginning Verify and Repair transaction
2018-02-23 23:44:49, Info                  CSI    00000189 [SR] Verify complete
2018-02-23 23:44:50, Info                  CSI    0000018a [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:44:50, Info                  CSI    0000018b [SR] Beginning Verify and Repair transaction
2018-02-23 23:45:00, Info                  CSI    0000018d [SR] Verify complete
2018-02-23 23:45:02, Info                  CSI    0000018e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:45:02, Info                  CSI    0000018f [SR] Beginning Verify and Repair transaction
2018-02-23 23:45:16, Info                  CSI    00000191 [SR] Verify complete
2018-02-23 23:45:17, Info                  CSI    00000192 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:45:17, Info                  CSI    00000193 [SR] Beginning Verify and Repair transaction
2018-02-23 23:45:33, Info                  CSI    00000197 [SR] Verify complete
2018-02-23 23:45:36, Info                  CSI    00000198 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:45:36, Info                  CSI    00000199 [SR] Beginning Verify and Repair transaction
2018-02-23 23:46:18, Info                  CSI    0000019b [SR] Verify complete
2018-02-23 23:46:20, Info                  CSI    0000019c [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:46:20, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
2018-02-23 23:46:43, Info                  CSI    000001a0 [SR] Verify complete
2018-02-23 23:46:44, Info                  CSI    000001a1 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:46:44, Info                  CSI    000001a2 [SR] Beginning Verify and Repair transaction
2018-02-23 23:46:54, Info                  CSI    000001a4 [SR] Verify complete
2018-02-23 23:46:55, Info                  CSI    000001a5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:46:55, Info                  CSI    000001a6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:47:04, Info                  CSI    000001a9 [SR] Verify complete
2018-02-23 23:47:05, Info                  CSI    000001aa [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:47:05, Info                  CSI    000001ab [SR] Beginning Verify and Repair transaction
2018-02-23 23:47:19, Info                  CSI    000001ad [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:18{9}]"sethc.exe" from store
2018-02-23 23:47:20, Info                  CSI    000001b0 [SR] Verify complete
2018-02-23 23:47:21, Info                  CSI    000001b1 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:47:21, Info                  CSI    000001b2 [SR] Beginning Verify and Repair transaction
2018-02-23 23:47:36, Info                  CSI    000001b4 [SR] Verify complete
2018-02-23 23:47:38, Info                  CSI    000001b5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:47:38, Info                  CSI    000001b6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:47:48, Info                  CSI    000001b8 [SR] Verify complete
2018-02-23 23:47:49, Info                  CSI    000001b9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:47:49, Info                  CSI    000001ba [SR] Beginning Verify and Repair transaction
2018-02-23 23:47:59, Info                  CSI    000001bc [SR] Verify complete
2018-02-23 23:48:00, Info                  CSI    000001bd [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:00, Info                  CSI    000001be [SR] Beginning Verify and Repair transaction
2018-02-23 23:48:09, Info                  CSI    000001c1 [SR] Verify complete
2018-02-23 23:48:10, Info                  CSI    000001c2 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:10, Info                  CSI    000001c3 [SR] Beginning Verify and Repair transaction
2018-02-23 23:48:19, Info                  CSI    000001c5 [SR] Verify complete
2018-02-23 23:48:20, Info                  CSI    000001c6 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:20, Info                  CSI    000001c7 [SR] Beginning Verify and Repair transaction
2018-02-23 23:48:27, Info                  CSI    000001ca [SR] Verify complete
2018-02-23 23:48:28, Info                  CSI    000001cb [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:28, Info                  CSI    000001cc [SR] Beginning Verify and Repair transaction
2018-02-23 23:48:39, Info                  CSI    000001cf [SR] Verify complete
2018-02-23 23:48:40, Info                  CSI    000001d0 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:40, Info                  CSI    000001d1 [SR] Beginning Verify and Repair transaction
2018-02-23 23:48:52, Info                  CSI    000001d4 [SR] Verify complete
2018-02-23 23:48:52, Info                  CSI    000001d5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:48:52, Info                  CSI    000001d6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:01, Info                  CSI    000001d9 [SR] Verify complete
2018-02-23 23:49:02, Info                  CSI    000001da [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:02, Info                  CSI    000001db [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:12, Info                  CSI    000001dd [SR] Verify complete
2018-02-23 23:49:14, Info                  CSI    000001de [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:14, Info                  CSI    000001df [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:30, Info                  CSI    000001e2 [SR] Verify complete
2018-02-23 23:49:30, Info                  CSI    000001e3 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:30, Info                  CSI    000001e4 [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:36, Info                  CSI    000001e6 [SR] Verify complete
2018-02-23 23:49:37, Info                  CSI    000001e7 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:37, Info                  CSI    000001e8 [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:43, Info                  CSI    000001ea [SR] Verify complete
2018-02-23 23:49:44, Info                  CSI    000001eb [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:44, Info                  CSI    000001ec [SR] Beginning Verify and Repair transaction
2018-02-23 23:49:50, Info                  CSI    000001ee [SR] Verify complete
2018-02-23 23:49:52, Info                  CSI    000001ef [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:49:52, Info                  CSI    000001f0 [SR] Beginning Verify and Repair transaction
2018-02-23 23:50:01, Info                  CSI    000001f2 [SR] Verify complete
2018-02-23 23:50:02, Info                  CSI    000001f3 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:50:02, Info                  CSI    000001f4 [SR] Beginning Verify and Repair transaction
2018-02-23 23:50:12, Info                  CSI    000001f6 [SR] Verify complete
2018-02-23 23:50:13, Info                  CSI    000001f7 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:50:13, Info                  CSI    000001f8 [SR] Beginning Verify and Repair transaction
2018-02-23 23:50:18, Info                  CSI    000001fa [SR] Verify complete
2018-02-23 23:50:19, Info                  CSI    000001fb [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:50:19, Info                  CSI    000001fc [SR] Beginning Verify and Repair transaction
2018-02-23 23:50:30, Info                  CSI    000001fe [SR] Verify complete
2018-02-23 23:50:30, Info                  CSI    000001ff [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:50:30, Info                  CSI    00000200 [SR] Beginning Verify and Repair transaction
2018-02-23 23:51:08, Info                  CSI    00000202 [SR] Verify complete
2018-02-23 23:51:09, Info                  CSI    00000203 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:51:09, Info                  CSI    00000204 [SR] Beginning Verify and Repair transaction
2018-02-23 23:51:50, Info                  CSI    00000206 [SR] Verify complete
2018-02-23 23:51:52, Info                  CSI    00000207 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:51:52, Info                  CSI    00000208 [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:07, Info                  CSI    0000020a [SR] Verify complete
2018-02-23 23:52:08, Info                  CSI    0000020b [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:08, Info                  CSI    0000020c [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:13, Info                  CSI    0000020e [SR] Verify complete
2018-02-23 23:52:14, Info                  CSI    0000020f [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:14, Info                  CSI    00000210 [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:21, Info                  CSI    00000212 [SR] Verify complete
2018-02-23 23:52:24, Info                  CSI    00000213 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:24, Info                  CSI    00000214 [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:35, Info                  CSI    00000216 [SR] Verify complete
2018-02-23 23:52:35, Info                  CSI    00000217 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:35, Info                  CSI    00000218 [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:44, Info                  CSI    0000021a [SR] Verify complete
2018-02-23 23:52:44, Info                  CSI    0000021b [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:44, Info                  CSI    0000021c [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:46, Info                  CSI    0000021e [SR] Verify complete
2018-02-23 23:52:46, Info                  CSI    0000021f [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:46, Info                  CSI    00000220 [SR] Beginning Verify and Repair transaction
2018-02-23 23:52:48, Info                  CSI    00000222 [SR] Verify complete
2018-02-23 23:52:50, Info                  CSI    00000223 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:52:50, Info                  CSI    00000224 [SR] Beginning Verify and Repair transaction
2018-02-23 23:53:07, Info                  CSI    0000022c [SR] Verify complete
2018-02-23 23:53:10, Info                  CSI    0000022d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:53:10, Info                  CSI    0000022e [SR] Beginning Verify and Repair transaction
2018-02-23 23:53:20, Info                  CSI    00000230 [SR] Verify complete
2018-02-23 23:53:22, Info                  CSI    00000231 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:53:22, Info                  CSI    00000232 [SR] Beginning Verify and Repair transaction
2018-02-23 23:53:27, Info                  CSI    00000234 [SR] Verify complete
2018-02-23 23:53:29, Info                  CSI    00000235 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:53:29, Info                  CSI    00000236 [SR] Beginning Verify and Repair transaction
2018-02-23 23:53:37, Info                  CSI    00000238 [SR] Verify complete
2018-02-23 23:53:39, Info                  CSI    00000239 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:53:39, Info                  CSI    0000023a [SR] Beginning Verify and Repair transaction
2018-02-23 23:53:50, Info                  CSI    0000023d [SR] Verify complete
2018-02-23 23:53:52, Info                  CSI    0000023e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:53:52, Info                  CSI    0000023f [SR] Beginning Verify and Repair transaction
2018-02-23 23:54:08, Info                  CSI    00000241 [SR] Verify complete
2018-02-23 23:54:09, Info                  CSI    00000242 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:54:09, Info                  CSI    00000243 [SR] Beginning Verify and Repair transaction
2018-02-23 23:54:12, Info                  CSI    00000245 [SR] Verify complete
2018-02-23 23:54:15, Info                  CSI    00000246 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:54:15, Info                  CSI    00000247 [SR] Beginning Verify and Repair transaction
2018-02-23 23:54:25, Info                  CSI    00000249 [SR] Verify complete
2018-02-23 23:54:27, Info                  CSI    0000024a [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:54:27, Info                  CSI    0000024b [SR] Beginning Verify and Repair transaction
2018-02-23 23:54:50, Info                  CSI    00000250 [SR] Verify complete
2018-02-23 23:54:52, Info                  CSI    00000251 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:54:52, Info                  CSI    00000252 [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:06, Info                  CSI    00000257 [SR] Verify complete
2018-02-23 23:55:08, Info                  CSI    00000258 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:08, Info                  CSI    00000259 [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:19, Info                  CSI    0000025c [SR] Verify complete
2018-02-23 23:55:20, Info                  CSI    0000025d [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:20, Info                  CSI    0000025e [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:30, Info                  CSI    0000026b [SR] Verify complete
2018-02-23 23:55:32, Info                  CSI    0000026c [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:32, Info                  CSI    0000026d [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:42, Info                  CSI    00000273 [SR] Verify complete
2018-02-23 23:55:43, Info                  CSI    00000274 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:43, Info                  CSI    00000275 [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:50, Info                  CSI    00000277 [SR] Verify complete
2018-02-23 23:55:51, Info                  CSI    00000278 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:51, Info                  CSI    00000279 [SR] Beginning Verify and Repair transaction
2018-02-23 23:55:56, Info                  CSI    0000027d [SR] Verify complete
2018-02-23 23:55:57, Info                  CSI    0000027e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:55:57, Info                  CSI    0000027f [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:07, Info                  CSI    00000283 [SR] Verify complete
2018-02-23 23:56:08, Info                  CSI    00000284 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:08, Info                  CSI    00000285 [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:18, Info                  CSI    000002a8 [SR] Verify complete
2018-02-23 23:56:19, Info                  CSI    000002a9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:19, Info                  CSI    000002aa [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:26, Info                  CSI    000002ac [SR] Verify complete
2018-02-23 23:56:27, Info                  CSI    000002ad [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:27, Info                  CSI    000002ae [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:34, Info                  CSI    000002b0 [SR] Verify complete
2018-02-23 23:56:35, Info                  CSI    000002b1 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:35, Info                  CSI    000002b2 [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:41, Info                  CSI    000002b4 [SR] Verify complete
2018-02-23 23:56:42, Info                  CSI    000002b5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:42, Info                  CSI    000002b6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:56:48, Info                  CSI    000002c4 [SR] Verify complete
2018-02-23 23:56:49, Info                  CSI    000002c5 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:56:49, Info                  CSI    000002c6 [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:04, Info                  CSI    000002c8 [SR] Verify complete
2018-02-23 23:57:06, Info                  CSI    000002c9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:06, Info                  CSI    000002ca [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:18, Info                  CSI    000002d8 [SR] Verify complete
2018-02-23 23:57:19, Info                  CSI    000002d9 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:19, Info                  CSI    000002da [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:23, Info                  CSI    000002dc [SR] Verify complete
2018-02-23 23:57:26, Info                  CSI    000002dd [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:26, Info                  CSI    000002de [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:37, Info                  CSI    000002e1 [SR] Verify complete
2018-02-23 23:57:38, Info                  CSI    000002e2 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:38, Info                  CSI    000002e3 [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:43, Info                  CSI    000002e5 [SR] Verify complete
2018-02-23 23:57:43, Info                  CSI    000002e6 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:43, Info                  CSI    000002e7 [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:46, Info                  CSI    000002e9 [SR] Verify complete
2018-02-23 23:57:47, Info                  CSI    000002ea [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:47, Info                  CSI    000002eb [SR] Beginning Verify and Repair transaction
2018-02-23 23:57:57, Info                  CSI    000002ed [SR] Verify complete
2018-02-23 23:57:58, Info                  CSI    000002ee [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:57:58, Info                  CSI    000002ef [SR] Beginning Verify and Repair transaction
2018-02-23 23:58:06, Info                  CSI    000002f1 [SR] Verify complete
2018-02-23 23:58:06, Info                  CSI    000002f2 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:58:06, Info                  CSI    000002f3 [SR] Beginning Verify and Repair transaction
2018-02-23 23:58:21, Info                  CSI    0000030d [SR] Verify complete
2018-02-23 23:58:22, Info                  CSI    0000030e [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:58:22, Info                  CSI    0000030f [SR] Beginning Verify and Repair transaction
2018-02-23 23:58:28, Info                  CSI    00000311 [SR] Verify complete
2018-02-23 23:58:29, Info                  CSI    00000312 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:58:29, Info                  CSI    00000313 [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:12, Info                  CSI    00000315 [SR] Verify complete
2018-02-23 23:59:13, Info                  CSI    00000316 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:13, Info                  CSI    00000317 [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:20, Info                  CSI    00000319 [SR] Verify complete
2018-02-23 23:59:21, Info                  CSI    0000031a [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:21, Info                  CSI    0000031b [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:26, Info                  CSI    0000031e [SR] Verify complete
2018-02-23 23:59:27, Info                  CSI    0000031f [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:27, Info                  CSI    00000320 [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:33, Info                  CSI    00000323 [SR] Verify complete
2018-02-23 23:59:34, Info                  CSI    00000324 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:34, Info                  CSI    00000325 [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:42, Info                  CSI    00000327 [SR] Verify complete
2018-02-23 23:59:43, Info                  CSI    00000328 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:43, Info                  CSI    00000329 [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:49, Info                  CSI    0000032b [SR] Verify complete
2018-02-23 23:59:50, Info                  CSI    0000032c [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:50, Info                  CSI    0000032d [SR] Beginning Verify and Repair transaction
2018-02-23 23:59:56, Info                  CSI    00000330 [SR] Verify complete
2018-02-23 23:59:57, Info                  CSI    00000331 [SR] Verifying 100 (0x0000000000000064) components
2018-02-23 23:59:57, Info                  CSI    00000332 [SR] Beginning Verify and Repair transaction
2018-02-24 00:00:11, Info                  CSI    00000334 [SR] Verify complete
2018-02-24 00:00:14, Info                  CSI    00000335 [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:00:14, Info                  CSI    00000336 [SR] Beginning Verify and Repair transaction
2018-02-24 00:00:39, Info                  CSI    00000338 [SR] Verify complete
2018-02-24 00:00:42, Info                  CSI    00000339 [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:00:42, Info                  CSI    0000033a [SR] Beginning Verify and Repair transaction
2018-02-24 00:01:00, Info                  CSI    0000033c [SR] Verify complete
2018-02-24 00:01:02, Info                  CSI    0000033d [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:01:02, Info                  CSI    0000033e [SR] Beginning Verify and Repair transaction
2018-02-24 00:01:21, Info                  CSI    00000341 [SR] Verify complete
2018-02-24 00:01:24, Info                  CSI    00000342 [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:01:24, Info                  CSI    00000343 [SR] Beginning Verify and Repair transaction
2018-02-24 00:01:42, Info                  CSI    00000345 [SR] Verify complete
2018-02-24 00:01:48, Info                  CSI    00000346 [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:01:48, Info                  CSI    00000347 [SR] Beginning Verify and Repair transaction
2018-02-24 00:02:09, Info                  CSI    00000349 [SR] Verify complete
2018-02-24 00:02:12, Info                  CSI    0000034a [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:02:12, Info                  CSI    0000034b [SR] Beginning Verify and Repair transaction
2018-02-24 00:02:30, Info                  CSI    0000034d [SR] Verify complete
2018-02-24 00:02:32, Info                  CSI    0000034e [SR] Verifying 100 (0x0000000000000064) components
2018-02-24 00:02:32, Info                  CSI    0000034f [SR] Beginning Verify and Repair transaction
2018-02-24 00:02:48, Info                  CSI    00000351 [SR] Verify complete
2018-02-24 00:02:48, Info                  CSI    00000352 [SR] Verifying 11 (0x000000000000000b) components
2018-02-24 00:02:48, Info                  CSI    00000353 [SR] Beginning Verify and Repair transaction
2018-02-24 00:02:49, Info                  CSI    00000355 [SR] Verify complete
2018-02-24 00:02:49, Info                  CSI    00000356 [SR] Repairing 1 components
2018-02-24 00:02:49, Info                  CSI    00000357 [SR] Beginning Verify and Repair transaction
2018-02-24 00:02:50, Info                  CSI    00000359 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:18{9}]"sethc.exe" from store
2018-02-24 00:02:50, Info                  CSI    0000035b [SR] Repair complete
2018-02-24 00:02:50, Info                  CSI    0000035c [SR] Committing transaction
2018-02-24 00:02:52, Info                  CSI    00000360 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired



#11 JSntgRvr

JSntgRvr

    Master Surgeon General


  • Malware Response Team
  • 11,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:02:28 AM

Posted 24 February 2018 - 02:25 PM

Excellent logs. Let us know if the issue returns.

No request for help throughout private messaging will be attended.

If I have helped you, consider making a donation to help me continue the fight against Malware!
btn_donate_SM.gif


#12 AhhhLeah

AhhhLeah
  • Topic Starter

  • Members
  • 139 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:02:28 AM

Posted 24 February 2018 - 02:28 PM

Everything going well so far.  Thank you so much for your time.  Much appreciated.



#13 hamluis

hamluis

    Moderator


  • Moderator
  • 55,754 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:28 AM

Posted 24 February 2018 - 04:14 PM

AII topic:  https://www.bleepingcomputer.com/forums/t/671681/searchscopes-pw-hijacked/ .

 

This Win 7 topic is now closed to avoid further confusion.

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users