[SOLVED] SFC - unable to repair corrupt files

D

DennisInOz

Contributor
Joined
Nov 1, 2015
Posts
27
I have a Lenovo E932 running Windows 10 64 bit.

I ran SFC /scannow. The report said SFC had fixed corrupted files. I ran SFC again and it again said it had fixed corrupted files. Each log file is attached. I rang SFC again, with the same result. I tried running DISM but got a message that it was unable to run.

I tried downloading and running SFCFix.exe but it crashed. A message said that crash logs had been sent to you.

In addition, my Windows 10 start menu has stopped working after a large Windows update. Cortana doesn't work, and I can't open the notification centre. I rebooted in safe mode, and the start menu worked fine. Maybe fixing the first problem will lead to the others being resolved. Very frustrating! Thank you in advance.
 

Attachments

I just ran SFC again. Log file is attached. Then I tried running SFCFix as administrator and got the following:
SFCFix Has Crashed


Something has gone horribly wrong and SFCFix has crashed. Would you like SFCFix
to submit a crash report to the developer so that this problem can be fixed?
Type "y" for yes or "n" for no and press enter to continue:

In addition, the latest Windows updates came through and were automatically installed -
Update for Windows 10 Version 1607 for x64-based Systems (KB3199986)
Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3201860)
Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954)

However, the computer would not restart after installation, and after 12 hours I rebooted it. Windows says all three were successfully installed.

Hope this helps.

Cheers,
Dennis
 

Attachments

Hello and Welcome Dennis,

Please try configuring Windows for Clean Boot for troubleshooting.

Clean Boot

  1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. Type msconfig in the search box, and then tap or click msconfig.
    2832179.png
  3. On the Services tab of the System Configuration dialog box, tap or click to select the Hide all Microsoft services check box, and then tap or click Disable all.
    2832144.png
  4. On the Startup tab of the System Configuration dialog box, tap or click Open Task Manager
    2832180.png
  5. On the Startup tab in Task Manager, for each startup item, select the item and then click Disable.
    2832181.png
  6. On the Startup tab of the System Configuration dialog box, tap or click OK, and then restart the computer.
    2832147.png


    https://support.microsoft.com/en-us/kb/929135

Restart your computer, then run DISM:

DISM /RestoreHealth Scan

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.

Please attach the CBS log even if DISM fails.
 
Thanks for getting back to me. Did as you asked and got:

"The remote procedure call failed.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log"

I have attached the CBS log you asked for, as well as the dism log.

Thanks,
Dennis
 

Attachments

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip

Step 2 - SFC Scan

  1. Swipe in from the right edge of the screen, and then tap Search.
    (If you're using a mouse, point to the upper-right corner of the screen, move the mouse pointer down, and then click Search.)
  2. Type cmd in the search box, and then right-click or press and hold on Command Prompt.
  3. Tap or click Run as administrator.
  4. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  5. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Hello again.

Content of SFC Fix file:

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-11-02 18:21:50.573
Microsoft Windows 10 Build 14393 - amd64
Using .zip script file at C:\Users\admin\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_10.0.14393.0_en-us_b41c3fccad4dfb8e

Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_10.0.14393.0_en-us_b41c3fccad4dfb8e\lsasrv.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_10.0.14393.0_en-us_b41c3fccad4dfb8e\lsasrv.dll.mui.

Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_10.0.14393.0_en-us_b41c3fccad4dfb8e
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_10.0.14393.0_en-us_b41c3fccad4dfb8e
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-11-02 18:21:52.370
Script hash: HfUUSRlUgU+ktkWzwFrMBvkVKz1uLhtzt3bKKFGRXh4=
----------------------EOF-----------------------

Zipped CBS file is also attached.

If I'm reading this correctly, hopefully the first part of my thread has been fixed, which is great.

I'm hoping now that you can help with my Windows 10 start button, etc. etc. and Windows update problem now. Look forward to hearing back.

Kind regards,
Dennis
 

Attachments

Run Windows Repairs
  1. Download Windows Repair (All-in-One) Portable to your desktop.
  2. Once the file is downloaded, right-click on the file on your desktop and choose Extract All...
    Extract.JPG
  3. Keep the defaults and click the Extract button.
  4. A folder named tweaking.com_windows_repair_aio will be extracted to the desktop. Once the extraction is complete the folder will open.
  5. Inside this folder, there is a folder named Tweaking.com - Windows Repair. Open this folder as well.
    Capture.JPG

  6. Double-click on Repair_Windows.exe to open. Note: Please make sure all of your programs are closed and anything you were working on is saved as we will be rebooting.
  7. When the program opens, click the Reboot to Safe Mode button at the bottom of the screen. Answer Yes to allow.
  8. Once rebooted into Safe Mode, open the program again. When the program opens, click the Repairs tab and click the Open Repairs button.
  9. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
  10. Please click the Unselect All button and then click to enable only the following ones:

    17 - Repair Windows Updates

  11. Ensure the Restart check box is selected and click the Start Repairs button in the lower right of the screen. This may take some time to run so be patient.
    StartRepairsWithReboot.JPG
  12. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.

Once complete, try running DISM again.

DISM /RestoreHealth Scan

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

  3. When DISM finishes scanning your component store, zip up and attach your CBS log to your next post:

    C:\Windows\Logs\CBS\CBS.log

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
Thank you. That all seemed to run smoothly, and CBS log is attached.

Start menu, etc., does not work yet, but I'm guessing there is more to do.

Kind regards,
Dennis
 

Attachments

Very good, the DISM log is clean.

Do you happen to be using Avast! antivirus?

I'd like to take a look at the event logs.

Event Log Collection

  • Download VEW by Vino Rosso here: VEW.EXE
  • Right click the file and select Run as administrator and click Continue or Allow at the User Account Control Prompt.
  • Click the check boxes next to Application and System located under Select log to query on the upper left.
  • Under Select type to list on the right click the boxes next to Error, Warning and Critical (not XP).
  • Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run.
  • Once it finishes it will display a log file in notepad.
  • Copy and paste its entire contents into your next reply.
 
No, not using Avast! I'm running Webroot.

Event log is:
Code: 
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 04/11/2016 7:40:15 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 03/11/2016 9:07:44 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 9:07:42 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 9:07:43 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchUI.exe, version: 10.0.14393.351, time stamp: 0x5801a548 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x184 Faulting application start time: 0x01d23616515e5897 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: 72cfcd72-9fbc-47bd-a925-78fe0cf046e2 Faulting package full name: Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI

Log: 'Application' Date/Time: 03/11/2016 9:07:41 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.187, time stamp: 0x57cf9d73 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1ce4 Faulting application start time: 0x01d23616508d0630 Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: bc1644fe-5003-4ba5-a916-2b197d0c1c45 Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.206_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: App

Log: 'Application' Date/Time: 03/11/2016 12:39:43 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 12:39:42 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: LockApp.exe, version: 0.0.0.0, time stamp: 0x57cf9cd3 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1968 Faulting application start time: 0x01d235cf5990ed08 Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: 4debfc78-f866-42b3-a5d7-60df9e0dd7aa Faulting package full name: Microsoft.LockApp_10.0.14393.0_neutral__cw5n1h2txyewy Faulting package-relative application ID: WindowsDefaultLockScreen

Log: 'Application' Date/Time: 03/11/2016 12:39:11 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 12:39:08 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: LockApp.exe, version: 0.0.0.0, time stamp: 0x57cf9cd3 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1834 Faulting application start time: 0x01d235cf458ec277 Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: b5e0d377-5ab0-4f6e-92d1-637fb1ca9fbd Faulting package full name: Microsoft.LockApp_10.0.14393.0_neutral__cw5n1h2txyewy Faulting package-relative application ID: WindowsDefaultLockScreen

Log: 'Application' Date/Time: 03/11/2016 12:38:41 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 12:08:58 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: LockApp.exe, version: 0.0.0.0, time stamp: 0x57cf9cd3 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x9b4 Faulting application start time: 0x01d235cb0e55e465 Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: 493671d9-6947-480b-8db3-2bb72768a7fd Faulting package full name: Microsoft.LockApp_10.0.14393.0_neutral__cw5n1h2txyewy Faulting package-relative application ID: WindowsDefaultLockScreen

Log: 'Application' Date/Time: 03/11/2016 6:53:32 AM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.LockApp_cw5n1h2txyewy!WindowsDefaultLockScreen failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 03/11/2016 1:56:30 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: LockApp.exe, version: 0.0.0.0, time stamp: 0x57cf9cd3 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0xa64 Faulting application start time: 0x01d235757eeb9d11 Faulting application path: C:\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\LockApp.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: f4b3e477-0388-4c43-9066-c4d90d36e5ef Faulting package full name: Microsoft.LockApp_10.0.14393.0_neutral__cw5n1h2txyewy Faulting package-relative application ID: WindowsDefaultLockScreen

Log: 'Application' Date/Time: 02/11/2016 10:40:37 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 02/11/2016 10:40:36 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.187, time stamp: 0x57cf9d73 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1504 Faulting application start time: 0x01d2355a21311b72 Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: e1430ce2-7f4c-4053-bbd6-4b1a00aeb4e5 Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.206_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: App

Log: 'Application' Date/Time: 02/11/2016 10:39:33 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 02/11/2016 10:39:32 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.187, time stamp: 0x57cf9d73 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1808 Faulting application start time: 0x01d23559fad643f9 Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: af5427b2-a1e7-4575-92b4-8bcb9aa9b515 Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.206_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: App

Log: 'Application' Date/Time: 02/11/2016 10:38:45 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 02/11/2016 10:38:44 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchUI.exe, version: 10.0.14393.351, time stamp: 0x5801a548 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x16e0 Faulting application start time: 0x01d23559de07279f Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: da03690b-8500-4424-8752-888c76ed54b3 Faulting package full name: Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI

Log: 'Application' Date/Time: 02/11/2016 10:38:42 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Log: 'Application' Date/Time: 02/11/2016 10:38:40 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SearchUI.exe, version: 10.0.14393.351, time stamp: 0x5801a548 Faulting module name: nvumdshimx.dll, version: 21.21.13.6909, time stamp: 0x579f36b5 Exception code: 0xc0000005 Fault offset: 0x0000000000051979 Faulting process id: 0x1568 Faulting application start time: 0x01d23559dc1b8422 Faulting application path: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe Faulting module path: C:\Windows\SYSTEM32\DriverStore\FileRepository\nvlawu.inf_amd64_575847cc3bb62ea3\nvumdshimx.dll Report Id: bdd7aab6-d464-4da0-9b1d-fb9299ab915f Faulting package full name: Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 03/11/2016 9:07:35 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 03/11/2016 2:38:44 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 03/11/2016 12:38:42 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 03/11/2016 10:53:36 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 03/11/2016 8:53:36 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 03/11/2016 6:53:34 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 03/11/2016 1:40:00 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 02/11/2016 11:40:00 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 02/11/2016 9:40:00 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=UserLogon(1)

Log: 'Application' Date/Time: 02/11/2016 9:39:49 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 02/11/2016 9:19:36 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=UserLogon(1)

Log: 'Application' Date/Time: 02/11/2016 9:19:17 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 02/11/2016 9:18:24 PM
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/11/2016 9:18:24 PM
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/11/2016 9:14:39 PM
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/11/2016 9:07:17 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

Log: 'Application' Date/Time: 02/11/2016 12:25:20 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 02/11/2016 10:25:20 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=TimerEvent

Log: 'Application' Date/Time: 02/11/2016 8:25:20 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=UserLogon(1)

Log: 'Application' Date/Time: 02/11/2016 8:25:11 AM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0x8007007B AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b13afb38-cd79-4ae5-9f7f-eed058d750ca Trigger=NetworkAvailable

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/10/2016 9:23:27 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 18/10/2016 12:32:20 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/10/2016 8:15:46 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/10/2016 1:50:10 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 13/10/2016 1:44:52 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 11/10/2016 4:49:10 AM
Type: Critical Category: 404
Event: 404 Source: Microsoft-Windows-TaskScheduler
Task Scheduler service has encountered RPC initialization error in "RpcServerUseProtseq:ncacn_ip_tcp". Additional Data: Error Value: 14.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/11/2016 12:08:58 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 03/11/2016 1:56:30 AM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:39:58 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}  and APPID  {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:39:58 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}  and APPID  {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:39:57 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:19:34 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}  and APPID  {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:19:34 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}  and APPID  {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:19:33 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 02/11/2016 9:18:24 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC}

Log: 'System' Date/Time: 02/11/2016 9:17:54 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

Log: 'System' Date/Time: 02/11/2016 9:17:49 PM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8}

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/11/2016 9:07:31 PM
Type: Warning Category: 0
Event: 27 Source: e1iexpress
Intel(R) Ethernet Connection I217-V  Network link is disconnected. 

Log: 'System' Date/Time: 03/11/2016 12:38:37 PM
Type: Warning Category: 0
Event: 27 Source: e1iexpress
Intel(R) Ethernet Connection I217-V  Network link is disconnected. 

Log: 'System' Date/Time: 03/11/2016 6:53:29 AM
Type: Warning Category: 0
Event: 27 Source: e1iexpress
Intel(R) Ethernet Connection I217-V  Network link is disconnected. 

Log: 'System' Date/Time: 02/11/2016 9:39:39 PM
Type: Warning Category: 414
Event: 414 Source: Microsoft-Windows-TaskScheduler
Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Office\Office 15 Subscription Heartbeat definition. Additional Data: Error Value: %ProgramFiles%\Common Files\Microsoft Shared\Office15\OLicenseHeartbeat.exe.

Log: 'System' Date/Time: 02/11/2016 9:19:08 PM
Type: Warning Category: 414
Event: 414 Source: Microsoft-Windows-TaskScheduler
Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Office\Office 15 Subscription Heartbeat definition. Additional Data: Error Value: %ProgramFiles%\Common Files\Microsoft Shared\Office15\OLicenseHeartbeat.exe.

Log: 'System' Date/Time: 02/11/2016 9:14:02 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 02/11/2016 9:14:02 PM
Type: Warning Category: 0
Event: 263 Source: Win32k
The event description cannot be found.

Log: 'System' Date/Time: 02/11/2016 9:07:24 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name win10.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 02/11/2016 9:07:13 PM
Type: Warning Category: 0
Event: 27 Source: e1iexpress
Intel(R) Ethernet Connection I217-V  Network link is disconnected. 

Log: 'System' Date/Time: 02/11/2016 8:25:02 AM
Type: Warning Category: 414
Event: 414 Source: Microsoft-Windows-TaskScheduler
Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Office\Office 15 Subscription Heartbeat definition. Additional Data: Error Value: %ProgramFiles%\Common Files\Microsoft Shared\Office15\OLicenseHeartbeat.exe.

Log: 'System' Date/Time: 02/11/2016 8:12:46 AM
Type: Warning Category: 414
Event: 414 Source: Microsoft-Windows-TaskScheduler
Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Office\Office 15 Subscription Heartbeat definition. Additional Data: Error Value: %ProgramFiles%\Common Files\Microsoft Shared\Office15\OLicenseHeartbeat.exe.

Log: 'System' Date/Time: 02/11/2016 6:59:40 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:59:38 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:59:38 AM
Type: Warning Category: 0
Event: 27 Source: e1iexpress
Intel(R) Ethernet Connection I217-V  Network link is disconnected. 

Log: 'System' Date/Time: 02/11/2016 6:56:54 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:56:43 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:56:39 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name win10.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 02/11/2016 6:56:30 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:56:29 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Log: 'System' Date/Time: 02/11/2016 6:56:29 AM
Type: Warning Category: 0
Event: 134 Source: Microsoft-Windows-Time-Service
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known.

Thank you.

Dennis
 
Glad to hear it! :thumbsup2:

I'll mark the thread solved. If you encounter any problems, please post back and I'll continue to assist you.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top