SkyWolf
Active member
Sorry i just read your previous post, changed the command of the first and it gave "Remote Prodecure Call failed" diiferent than the second one.
Windows Update DISM.exe error 87 / TrustedInstaller error 1067
- Thread starter SkyWolf
- Start date
BrianDrab
Emeritus
Thanks. Can you uninstall IE 11? If you follow the article, you only need to do steps 1-6.
http://www.wikihow.com/Uninstall-Internet-Explorer-11-for-Windows-7
http://www.wikihow.com/Uninstall-Internet-Explorer-11-for-Windows-7
SkyWolf
Active member
Internet Explorer doesn't show up on Programs and Features, strange thing is i do have it and use it ocassionaly, i tried unistalling it from cmd and i got both "The remote procedure call failed" and ""Access is denied" errors, mostly the first one.
BrianDrab
Emeritus
OK, thanks. Please do the following.
Step#1 - 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...
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.
6. Double-click on Repair_Windows.exe to open.
7. When the program opens, click the Repairs tab and click the Open Repairs button.
8. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
9. Please click the Unselect All button and then click to enable only the following ones:
01 - Reset Registry Permissions
02 - Reset File Permissions
03 - Reset Service Permissions
04 - Register System Files
05 - Repair WMI
06 - Repair Windows Firewall
10 - Remove Policies Set By Infection
13 - Repair Winsock & DNS Cache
15 - Repair Proxy Settings
17 - Repair Windows Updates
21 - Repair MSI (Windows Installer)
10. 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.
11. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.
Let me know once this is complete. Thanks.
Step#1 - 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...
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.
6. Double-click on Repair_Windows.exe to open.
7. When the program opens, click the Repairs tab and click the Open Repairs button.
8. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
9. Please click the Unselect All button and then click to enable only the following ones:
01 - Reset Registry Permissions
02 - Reset File Permissions
03 - Reset Service Permissions
04 - Register System Files
05 - Repair WMI
06 - Repair Windows Firewall
10 - Remove Policies Set By Infection
13 - Repair Winsock & DNS Cache
15 - Repair Proxy Settings
17 - Repair Windows Updates
21 - Repair MSI (Windows Installer)
10. 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.
11. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.
Let me know once this is complete. Thanks.
SkyWolf
Active member
Just now finished running the selected fixes, while it was running i suddenly saw the WU logo on my taskbar automatically downloading updates, thing it hasn't done before, but as far as i checked i still have the same errors.
BrianDrab
Emeritus
In your very first post, one of the things you said you tried was to go to a command-prompt and type net start trustedinstaller and hit enter. You received a System error 1067. Can you try this again and let me know if you get the same error?
SkyWolf
Active member
Same error again :s
BrianDrab
Emeritus
Thanks. Please do the following.
Step#1 - Retrieve Event Log Messages
1. Download Event Viewer Tool by Vino Rosso to your Desktop
2. Right-click on the file (VEW.exe) and select Run as administrator.
3. Check the options as shown below and put 20 in for the number of events.
4. Click Run. After a few moments, notepad will open with the contents of the Event Logs. Please copy and paste these in your next post. Thank you.
Step#1 - Retrieve Event Log Messages
1. Download Event Viewer Tool by Vino Rosso to your Desktop
2. Right-click on the file (VEW.exe) and select Run as administrator.
3. Check the options as shown below and put 20 in for the number of events.
4. Click Run. After a few moments, notepad will open with the contents of the Event Logs. Please copy and paste these in your next post. Thank you.
SkyWolf
Active member
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 27/05/2015 2:15:08 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:32 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:03 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:27:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:27:32 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:32 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:27:32 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:52 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:33 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:24 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:25:28 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:35 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:28 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:18 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:00 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:23:53 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 05/04/2015 5:03:55 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: 05/03/2015 5:13:50 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: 05/04/2015 5:27:35 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: 04/04/2015 5:38:38 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: 04/04/2015 11:43:28 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: 03/04/2015 6:19:40 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: 30/03/2015 6:05:09 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: 30/03/2015 6:00:39 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: 30/03/2015 6:00:40 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: 29/03/2015 6:03:58 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: 28/03/2015 6:03:47 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: 27/03/2015 8:00:50 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: 28/03/2015 6:03:53 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: 27/03/2015 6:05: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: 27/03/2015 6:06:32 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: 26/03/2015 6:00:46 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: 25/03/2015 6:04:35 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: 23/03/2015 6:03:47 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: 23/03/2015 6:00:49 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: 23/03/2015 6:10:25 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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/05/2015 7:16:10 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 68 time(s).
Log: 'System' Date/Time: 27/05/2015 7:16:10 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:15:40 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 67 time(s).
Log: 'System' Date/Time: 27/05/2015 7:15:40 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:15:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 66 time(s).
Log: 'System' Date/Time: 27/05/2015 7:15:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:14:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 65 time(s).
Log: 'System' Date/Time: 27/05/2015 7:14:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:14:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 64 time(s).
Log: 'System' Date/Time: 27/05/2015 7:14:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:48 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 63 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:48 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 62 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 61 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:12:46 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 60 time(s).
Log: 'System' Date/Time: 27/05/2015 7:12:46 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:12:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 59 time(s).
Log: 'System' Date/Time: 27/05/2015 7:12:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/05/2015 6:23:20 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 27/05/2015 6:23:10 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\a2p52e4e failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 27/05/2015 6:22:53 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\a2p52e4e failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 27/05/2015 9:26:56 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 27/05/2015 7:19:18 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name chat.la1.lol.riotgames.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:54 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:52 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name sync.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:46 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:20 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:19 AM
Type: Warning Category: 0
Event: 1006 Source: Microsoft-Windows-DNS-Client
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. 10.2.9.164
Log: 'System' Date/Time: 27/05/2015 7:17:19 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name Microsoft – Official Home Page timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:17 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name api.zenguard.biz timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:10 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name lolicore.ch | lolicore75rq3tm5.onion - lolicore and speedcore archive timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:15:14 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ekg.riotgames.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 26/05/2015 11:34:34 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 26/05/2015 11:34:26 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\au6dx0t4 failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 26/05/2015 11:34:16 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\au6dx0t4 failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 26/05/2015 8:02:22 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 26/05/2015 7:23:31 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 26/05/2015 7:23:22 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\ai2g6eli failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Report run at 27/05/2015 2:15:08 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:32 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:28:03 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:28:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:27:33 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:27:32 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Error Category: 1
Event: 1006 Source: Microsoft-Windows-Search
The Windows Search Service has failed to create the new search index. Internal error <1, 0x80070005, Failed to add Gather Application: Windows>.
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 27/05/2015 6:31:39 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:30:09 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:30:03 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:29:33 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:29:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:32 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:18 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:28:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:27:32 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:27:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:52 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:33 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:24 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:26:02 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:25:28 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:35 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:28 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:18 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:24:00 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
Log: 'Application' Date/Time: 27/05/2015 6:23:53 PM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 05/04/2015 5:03:55 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: 05/03/2015 5:13:50 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: 05/04/2015 5:27:35 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: 04/04/2015 5:38:38 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: 04/04/2015 11:43:28 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: 03/04/2015 6:19:40 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: 30/03/2015 6:05:09 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: 30/03/2015 6:00:39 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: 30/03/2015 6:00:40 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: 29/03/2015 6:03:58 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: 28/03/2015 6:03:47 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: 27/03/2015 8:00:50 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: 28/03/2015 6:03:53 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: 27/03/2015 6:05: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: 27/03/2015 6:06:32 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: 26/03/2015 6:00:46 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: 25/03/2015 6:04:35 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: 23/03/2015 6:03:47 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: 23/03/2015 6:00:49 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: 23/03/2015 6:10:25 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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/05/2015 7:16:10 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 68 time(s).
Log: 'System' Date/Time: 27/05/2015 7:16:10 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:15:40 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 67 time(s).
Log: 'System' Date/Time: 27/05/2015 7:15:40 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:15:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 66 time(s).
Log: 'System' Date/Time: 27/05/2015 7:15:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:14:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 65 time(s).
Log: 'System' Date/Time: 27/05/2015 7:14:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:14:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 64 time(s).
Log: 'System' Date/Time: 27/05/2015 7:14:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:48 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 63 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:48 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 62 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:13:09 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 61 time(s).
Log: 'System' Date/Time: 27/05/2015 7:13:09 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:12:46 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 60 time(s).
Log: 'System' Date/Time: 27/05/2015 7:12:46 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
Log: 'System' Date/Time: 27/05/2015 7:12:39 PM
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The Windows Search service terminated unexpectedly. It has done this 59 time(s).
Log: 'System' Date/Time: 27/05/2015 7:12:39 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Windows Search service terminated with the following error: Access is denied.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 27/05/2015 6:23:20 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 27/05/2015 6:23:10 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\a2p52e4e failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 27/05/2015 6:22:53 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\a2p52e4e failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 27/05/2015 9:26:56 AM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 27/05/2015 7:19:18 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name chat.la1.lol.riotgames.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:54 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:52 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name sync.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:46 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:20 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name push.opera.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:19 AM
Type: Warning Category: 0
Event: 1006 Source: Microsoft-Windows-DNS-Client
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. 10.2.9.164
Log: 'System' Date/Time: 27/05/2015 7:17:19 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name Microsoft – Official Home Page timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:17 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name api.zenguard.biz timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:17:10 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name lolicore.ch | lolicore75rq3tm5.onion - lolicore and speedcore archive timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 27/05/2015 7:15:14 AM
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ekg.riotgames.com timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 26/05/2015 11:34:34 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 26/05/2015 11:34:26 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\au6dx0t4 failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 26/05/2015 11:34:16 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\au6dx0t4 failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
Log: 'System' Date/Time: 26/05/2015 8:02:22 PM
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.
Log: 'System' Date/Time: 26/05/2015 7:23:31 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.
Log: 'System' Date/Time: 26/05/2015 7:23:22 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\ai2g6eli failed to load for the device PCI\VEN_105A&DEV_3318&SUBSYS_CDF46EAF&REV_01\4&5d18f2df&1.
BrianDrab
Emeritus
Thank you. Please do the following.
Step#1 - Examine Permissions
Step#1 - Examine Permissions
- Click Start -> Inside the search field search for Powershell.exe
- Right-Click on Powershell in the search results and select Run as administrator.
- Inside the PowerShell windows copy the following commands (one by one) and press enter after each line.
get-acl "C:\ProgramData\Microsoft\Search\Data\" | format-list >2
get-acl "C:\Windows\Temp\" | format-list >>2
notepad 2 - You should now have a notepad file with all the security permissions for these folders. Please post the contents back into this thread.
SkyWolf
Active member
Sorry for the late response:
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\Search\
Data\
Owner : SKYWOLF\Wolfcer
Group : NT AUTHORITY\SYSTEM
Access : SKYWOLF\Wolfcer Allow FullControl
SKYWOLF\Wolfcer Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:SYD
A;OIIOID;FA;;;S-
1-5-21-3568495232-3014248763-797569959-1000)(A;CIID;FA;;;S-1-5-21-3568
495232-3014248763-797569959-1000)
Path : Microsoft.PowerShell.Core\FileSystem::C:\Windows\Temp\
Owner : SKYWOLF\Wolfcer
Group : BUILTIN\Administradores
Access : Everyone Allow FullControl
CREATOR OWNER Allow 268435456
NT AUTHORITY\SYSTEM Allow FullControl
BUILTIN\Administradores Allow FullControl
BUILTIN\Usuarios Allow FullControl
NT SERVICE\TrustedInstaller Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:BAD
AI(A;OICI;FA;;;W
D)(A;OICIIO;GA;;;CO)(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;FA;;;BU)(A
;OICI;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478
464)
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\Search\
Data\
Owner : SKYWOLF\Wolfcer
Group : NT AUTHORITY\SYSTEM
Access : SKYWOLF\Wolfcer Allow FullControl
SKYWOLF\Wolfcer Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:SYD
A;OIIOID;FA;;;S-1-5-21-3568495232-3014248763-797569959-1000)(A;CIID;FA;;;S-1-5-21-3568
495232-3014248763-797569959-1000)
Path : Microsoft.PowerShell.Core\FileSystem::C:\Windows\Temp\
Owner : SKYWOLF\Wolfcer
Group : BUILTIN\Administradores
Access : Everyone Allow FullControl
CREATOR OWNER Allow 268435456
NT AUTHORITY\SYSTEM Allow FullControl
BUILTIN\Administradores Allow FullControl
BUILTIN\Usuarios Allow FullControl
NT SERVICE\TrustedInstaller Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:BAD
AI(A;OICI;FA;;;WD)(A;OICIIO;GA;;;CO)(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;FA;;;BU)(A
;OICI;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478
464)
BrianDrab
Emeritus
I see some missing permissions causing the following error on your system. I need to gather a little more info and then we can fix. Please do the following.
Step#1 - Examine Permissions
Code:
Log: 'Application' Date/Time: 27/05/2015 6:28:02 PM
Type: Error Category: 3
Event: 3030 Source: Microsoft-Windows-Search
The gatherer service cannot be initialized.
Details:
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. (HRESULT : 0x80070660) (0x80070660)Step#1 - Examine Permissions
- Click Start -> Inside the search field search for Powershell.exe
- Right-Click on Powershell in the search results and select Run as administrator.
- Inside the PowerShell windows copy the following commands (one by one) and press enter after each line.
get-acl "C:\ProgramData\Microsoft\Search\" | format-list >2
get-acl "C:\ProgramData\Microsoft\" | format-list >>2
notepad 2 - You should now have a notepad file with all the security permissions for these folders. Please post the contents back into this thread.
SkyWolf
Active member
That could be it as i modified permissions several times, even changed my profile path ("wolfcer" to the actual "wolf") with some folders still having my old path as the owner:
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\Search\
Owner : SKYWOLF\Wolfcer
Group : NT AUTHORITY\SYSTEM
Access : SKYWOLF\Wolfcer Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:SYD(A;OICI;FA;;;S-1
-5-21-3568495232-3014248763-797569959-1000)
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\
Owner : SKYWOLF\Wolfcer
Group : BUILTIN\Administradores
Access : Everyone Allow FullControl
NT AUTHORITY\SYSTEM Allow FullControl
BUILTIN\Administradores Allow FullControl
BUILTIN\Usuarios Allow FullControl
NT SERVICE\TrustedInstaller Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:BADAI(A;OICI;FA;;;W
D)(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;FA;;;BU)(A;OICI;FA;;;S-1-5-8
0-956008885-3418522649-1831038044-1853292631-2271478464)
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\Search\
Owner : SKYWOLF\Wolfcer
Group : NT AUTHORITY\SYSTEM
Access : SKYWOLF\Wolfcer Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:SYD
(A;OICI;FA;;;S-1-5-21-3568495232-3014248763-797569959-1000)
Path : Microsoft.PowerShell.Core\FileSystem::C:\ProgramData\Microsoft\
Owner : SKYWOLF\Wolfcer
Group : BUILTIN\Administradores
Access : Everyone Allow FullControl
NT AUTHORITY\SYSTEM Allow FullControl
BUILTIN\Administradores Allow FullControl
BUILTIN\Usuarios Allow FullControl
NT SERVICE\TrustedInstaller Allow FullControl
Audit :
Sddl : O:S-1-5-21-3568495232-3014248763-797569959-1000G:BAD
AI(A;OICI;FA;;;WD)(A;OICI;FA;;;SY)(A;OICI;FA;;;BA)(A;OICI;FA;;;BU)(A;OICI;FA;;;S-1-5-8
0-956008885-3418522649-1831038044-1853292631-2271478464)
BrianDrab
Emeritus
OK, please do the following.
Add System Permissions Back
1. Navigate to C:\ProgramData\Microsoft\
2. Right-click on the Search folder and select Properties.
3. Click the Security tab.
4. Click the Advanced button.
5. Click the Change Permissions button.
6. Check the Include inheritable permissions from the object's parent checkbox.
7. Click OK on each of the three forms that are up to close out of them.
Repeat these steps on the Data folder located at C:\ProgramData\Microsoft\Search
Let me know when this is done or if you had any issues with this.
Add System Permissions Back
1. Navigate to C:\ProgramData\Microsoft\
2. Right-click on the Search folder and select Properties.
3. Click the Security tab.
4. Click the Advanced button.
5. Click the Change Permissions button.
6. Check the Include inheritable permissions from the object's parent checkbox.
7. Click OK on each of the three forms that are up to close out of them.
Repeat these steps on the Data folder located at C:\ProgramData\Microsoft\Search
Let me know when this is done or if you had any issues with this.
SkyWolf
Active member
Done without trouble, the "Search" folder appeared with the lock and now's gone.
BrianDrab
Emeritus
Good. At least that error is likely fixed. I suspect there are more permission problems. Please do the following.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and do the Net Start TrustedInstaller command again.
3. Stop Process Monitor as soon as you receive the System error 1067. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and do the Net Start TrustedInstaller command again.
3. Stop Process Monitor as soon as you receive the System error 1067. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML
SkyWolf
Active member
It finally starts and stops as intended, i think this was on my side since i use and app to manage process and it was terminating it everytime.
Here's the log: Logfile.pml
Here's the log: Logfile.pml
BrianDrab
Emeritus
Good News. So are you having any other issues?
SkyWolf
Active member
I tried running sfc again and it stops at 23%:
Also tried installing some updates and this time it appears it installs them, but after restarting the same updates appear again as downloadable.
Also tried installing some updates and this time it appears it installs them, but after restarting the same updates appear again as downloadable.
BrianDrab
Emeritus
That's progress.
Please zip and send me the C:\Windows\Logs\CBS\CBS.log file.
Please zip and send me the C:\Windows\Logs\CBS\CBS.log file.
Has Sysnative Forums helped you? Please consider donating to help us support the site!