Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows Indexing


  • Please log in to reply

#91
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP

If you are not using the mouspad it would be wise to disable it.  I just had one where the mousepad was causing all sorts of strange things to happen.


  • 0

Advertisements


#92
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Okay.  How do I do that?  I looked in the device manager and in the properties.  The only option it gives it to uninstall it.


Edited by A1RotNBrat, 15 January 2016 - 07:55 AM.

  • 0

#93
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP

Should be something in Control panel.  IF not a separate item then look under Mouse, there's sometimes a separate tab.


  • 0

#94
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Finally found it.  It had to be turned off in the Vaio controls. I rebooted and it's not "clicking" as much but it is still selecting.  As for that update that locks up, how can I find out how to uninstall or delete it so it won't keep trying to update.


  • 0

#95
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP

By Selecting you mean when you change tabs you get the blue?

 

Try changing tabs without the mouse.  Ctrl + 1 should select the first tab, Ctrl + 2 the second.  Does it still do it?

 

As for that update that locks up, how can I find out how to uninstall or delete it so it won't keep trying to update.

 

 

 

Which update is that?


  • 0

#96
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

No it didn't do it when I used the Control.  Also, it opens more than one tab if a click on a link.  Ex.  I just clicked in my email to open this page and it opened it twice.   I have no idea which update it is.  It is the same one that I left running all night when were cleaning up the windows search.  I has tried to update every other time I reboot and it hangs up on "update 2 of 3".


  • 0

#97
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP

If you reactivate the mousepad and disconnect your mouse does it still do odd stuff?

 

Run VEW again and let's see if there are any errors about your update.  There should also be something in Windows Updates, History if the update is failing.

  1. Open Windows Update by swiping in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), tapping or clicking Settings, tapping or clicking Change PC settings, and then tapping or clicking Update and recovery.

  2. Tap or click View your update history.


  • 0

#98
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 17/01/2016 7:39:58 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 15/01/2016 11:24:28 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 15/01/2016 11:24: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.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 17/01/2016 1:33:08 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the YahooAUService service.
 
Log: 'System' Date/Time: 17/01/2016 10:48:43 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 17/01/2016 10:48:43 AM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 16/01/2016 4:20:35 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 16/01/2016 4:20:35 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 16/01/2016 12:49:22 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 16/01/2016 12:48:04 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 2:13:16 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 2:13:16 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 2:06:27 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 2:06:27 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 1:29:38 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 1:28:36 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 12:25:22 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The AppX Deployment Service (AppXSVC) service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.
 
Log: 'System' Date/Time: 15/01/2016 12:25:22 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect.
 
Log: 'System' Date/Time: 15/01/2016 12:22:05 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Fax - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 12:22:05 PM
Type: Error Category: 1
Event: 20 Source: Microsoft-Windows-WindowsUpdateClient
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.
 
Log: 'System' Date/Time: 15/01/2016 12:17:08 PM
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The exact nature of the corruption is unknown.  The file system structures need to be scanned online. 
 
Log: 'System' Date/Time: 15/01/2016 11:24:19 AM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
 
Log: 'System' Date/Time: 15/01/2016 11:24:51 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 5:10:27 AM on ?1/?15/?2016 was unexpected.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 17/01/2016 1:33:59 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 17/01/2016 11:55:03 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name i.e.sallybeauty.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 16/01/2016 9:00:55 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name sync.1rx.io timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 16/01/2016 6:00:37 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name win8.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 16/01/2016 4:57:11 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name _ldap._tcp.dc._msdcs.mshome.net. timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 16/01/2016 4:56:04 PM
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: 16/01/2016 4:35:32 PM
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: 16/01/2016 4:35:30 PM
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: 16/01/2016 3:16:19 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name s-static.ak.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/01/2016 9:02:09 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 0-edge-chat.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/01/2016 8:01:07 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 15/01/2016 7:59:58 PM
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: 15/01/2016 7:59:57 PM
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: 15/01/2016 11:29:33 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 223.20.215.181.in-addr.arpa. timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 15/01/2016 11:24:35 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 14/01/2016 10:28:08 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 3-edge-chat.facebook.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 14/01/2016 9:22:21 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 14/01/2016 4:59:33 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name aax.amazon-adsystem.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 14/01/2016 4:06:51 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_0BB4&PID_0BAD&MI_00\6&540db0c&0&0000.
 
Log: 'System' Date/Time: 14/01/2016 1:17:18 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name node-p1w-oloh8e.sitescout.com timed out after none of the configured DNS servers responded.

  • 0

#99
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 17/01/2016 7:41:48 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 17/01/2016 10:47:16 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 76a4  Start Time: 01d151143c728523  Termination Time: 4294967295  Application Path: C:\WINDOWS\syswow64\backgroundTaskHost.exe  Report Id: a71cfe7d-bd07-11e5-bf91-a343d73ea42f  Faulting package full name: LogosBibleSoftware.Vyrso_1.2.0.3_x86__h0wrhs0ttj2c8  Faulting package-relative application ID: App 
 
Log: 'Application' Date/Time: 16/01/2016 4:56:04 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 347281
 
Log: 'Application' Date/Time: 16/01/2016 4:56:04 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 347281
 
Log: 'Application' Date/Time: 16/01/2016 4:56:02 PM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second
 
Log: 'Application' Date/Time: 16/01/2016 4:02:32 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: backgroundTaskHost.exe, version: 6.3.9600.17415, time stamp: 0x54503d58 Faulting module name: combase.dll, version: 6.3.9600.17415, time stamp: 0x54503d84 Exception code: 0xc000027b Fault offset: 0x001212e1 Faulting process id: 0x6ec Faulting application start time: 0x01d150774a0ae9b8 Faulting application path: C:\WINDOWS\syswow64\backgroundTaskHost.exe Faulting module path: C:\WINDOWS\SYSTEM32\combase.dll Report Id: 8cb8ceee-bc6a-11e5-bf91-a343d73ea42f Faulting package full name: LogosBibleSoftware.Vyrso_1.2.0.3_x86__h0wrhs0ttj2c8 Faulting package-relative application ID: App
 
Log: 'Application' Date/Time: 15/01/2016 8:01:54 PM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.WindowsPhone_8wekyb3d8bbwe!windowsphone.App failed with error: The app manager is required to activate applications, but is not running. See the Microsoft-Windows-TWinUI/Operational log for additional information.
 
Log: 'Application' Date/Time: 15/01/2016 4:09:57 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: backgroundTaskHost.exe, version: 6.3.9600.17415, time stamp: 0x54503d58 Faulting module name: combase.dll, version: 6.3.9600.17415, time stamp: 0x54503d84 Exception code: 0xc000027b Fault offset: 0x001212e1 Faulting process id: 0x217c Faulting application start time: 0x01d14faf29e8a5b8 Faulting application path: C:\WINDOWS\syswow64\backgroundTaskHost.exe Faulting module path: C:\WINDOWS\SYSTEM32\combase.dll Report Id: 6b21d8a6-bba2-11e5-bf90-9a225f119c61 Faulting package full name: LogosBibleSoftware.Vyrso_1.2.0.3_x86__h0wrhs0ttj2c8 Faulting package-relative application ID: App
 
Log: 'Application' Date/Time: 15/01/2016 12:37:17 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: wwahost.exe, version: 6.3.9600.17415, time stamp: 0x545036ce Faulting module name: twinapi.appcore.dll, version: 6.3.9600.17415, time stamp: 0x54503c4d Exception code: 0xc000027b Fault offset: 0x0000000000063c1f Faulting process id: 0x1d18 Faulting application start time: 0x01d14f915c36ec2e Faulting application path: C:\WINDOWS\system32\wwahost.exe Faulting module path: C:\Windows\System32\twinapi.appcore.dll Report Id: b5ade2ea-bb84-11e5-bf90-9a225f119c61 Faulting package full name: Microsoft.WindowsPhone_1.42.1701.1_x64__8wekyb3d8bbwe Faulting package-relative application ID: windowsphone.App
 
Log: 'Application' Date/Time: 15/01/2016 12:14:05 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program backgroundTaskHost.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: b5c  Start Time: 01d14f8d7ff84a9e  Termination Time: 4294967295  Application Path: C:\WINDOWS\syswow64\backgroundTaskHost.exe  Report Id: 731a5f9b-bb81-11e5-bf90-9a225f119c61  Faulting package full name: LogosBibleSoftware.Vyrso_1.2.0.3_x86__h0wrhs0ttj2c8  Faulting package-relative application ID: App 
 
Log: 'Application' Date/Time: 15/01/2016 11:26:35 AM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.WindowsPhone_8wekyb3d8bbwe!windowsphone.App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
 
Log: 'Application' Date/Time: 15/01/2016 11:26:35 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program wwahost.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 1204  Start Time: 01d14f877b150c9e  Termination Time: 4294967295  Application Path: C:\WINDOWS\system32\wwahost.exe  Report Id: c5ed70d2-bb7a-11e5-bf90-9a225f119c61  Faulting package full name: Microsoft.WindowsPhone_1.42.1701.1_x64__8wekyb3d8bbwe  Faulting package-relative application ID: windowsphone.App 
 
Log: 'Application' Date/Time: 15/01/2016 11:26:02 AM
Type: Error Category: 2414
Event: 2486 Source: Microsoft-Windows-Immersive-Shell
App Microsoft.WindowsPhone_1.42.1701.1_x64__8wekyb3d8bbwe+windowsphone.App did not launch within its allotted time.
 
Log: 'Application' Date/Time: 15/01/2016 10:54:29 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MsiExec.exe, version: 5.0.9600.17905, time stamp: 0x557f547f Faulting module name: msvcrt.dll, version: 7.0.9600.17415, time stamp: 0x545055fe Exception code: 0xc00000fd Fault offset: 0x00000000000022de Faulting process id: 0x323c Faulting application start time: 0x01d14f830fa87eda Faulting application path: C:\Windows\System32\MsiExec.exe Faulting module path: C:\WINDOWS\system32\msvcrt.dll Report Id: 5956e6d7-bb76-11e5-bf8f-899424516ed9 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 15/01/2016 7:44:54 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledSPRetry 1141
 
Log: 'Application' Date/Time: 15/01/2016 7:44:54 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: m->NextScheduledEvent 1141
 
Log: 'Application' Date/Time: 15/01/2016 7:44:54 AM
Type: Error Category: 0
Event: 100 Source: Bonjour Service
Task Scheduling Error: Continuously busy for more than a second
 
Log: 'Application' Date/Time: 15/01/2016 4:47:57 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SetupHost.Exe, version: 10.0.10586.0, time stamp: 0x5632d702 Faulting module name: ntdll.dll, version: 6.3.9600.18185, time stamp: 0x5683f0c5 Exception code: 0xc0000005 Fault offset: 0x000000000005503e Faulting process id: 0x2314 Faulting application start time: 0x01d14f4a921f5bdd Faulting application path: C:\$WINDOWS.~BT\Sources\SetupHost.Exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 256dbdfa-bb43-11e5-bf8f-899424516ed9 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 15/01/2016 1:33:38 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SetupHost.Exe, version: 10.0.10586.0, time stamp: 0x5632d702 Faulting module name: ntdll.dll, version: 6.3.9600.18185, time stamp: 0x5683f0c5 Exception code: 0xc0000005 Fault offset: 0x000000000005503e Faulting process id: 0x1eb8 Faulting application start time: 0x01d14f2d3cf55a38 Faulting application path: C:\$WINDOWS.~BT\Sources\SetupHost.Exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: fff5ad5e-bb27-11e5-bf8f-899424516ed9 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 15/01/2016 1:22:12 AM
Type: Error Category: 5973
Event: 5973 Source: Microsoft-Windows-Immersive-Shell
Activation of app Microsoft.WindowsPhone_8wekyb3d8bbwe!windowsphone.App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
 
Log: 'Application' Date/Time: 15/01/2016 1:22:12 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program wwahost.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 22f8  Start Time: 01d14f3318b6eff5  Termination Time: 4294967295  Application Path: C:\WINDOWS\system32\wwahost.exe  Report Id: 60a9b320-bb26-11e5-bf8f-899424516ed9  Faulting package full name: Microsoft.WindowsPhone_1.42.1701.1_x64__8wekyb3d8bbwe  Faulting package-relative application ID: windowsphone.App 
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/01/2016 9:33:57 PM
Type: Warning Category: 7
Event: 507 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 1499136 (0x000000000016e000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (84 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2940928 (0x00000000002ce000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2891776 (0x00000000002c2000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2899968 (0x00000000002c4000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2908160 (0x00000000002c6000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2932736 (0x00000000002cc000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2867200 (0x00000000002bc000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:55 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2875392 (0x00000000002be000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:47 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2826240 (0x00000000002b2000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:47 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2850816 (0x00000000002b8000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:47 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2859008 (0x00000000002ba000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:47 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2809856 (0x00000000002ae000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:43 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2801664 (0x00000000002ac000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:43 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2793472 (0x00000000002aa000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:43 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2613248 (0x000000000027e000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:43 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2777088 (0x00000000002a6000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:43 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2768896 (0x00000000002a4000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:33 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2465792 (0x000000000025a000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:29 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2072576 (0x00000000001fa000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
 
Log: 'Application' Date/Time: 15/01/2016 9:33:29 PM
Type: Warning Category: 1
Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2064384 (0x00000000001f8000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

  • 0

#100
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

Here are three screenshots from the Window's Update showing what has succeeded and failed.  I just went back to the 1st.  

Attached Thumbnails

  • Update.png
  • update2.png
  • update3.png

  • 0

Advertisements


#101
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP
Installation Failure: Windows failed to install the following update with error 0x80070002: Hewlett-Packard  - Imaging, Other hardware - Null Print - HP Photosmart 7520 series.

 

 

The update culprit is your HP Photosmart 7520.  I would uninstall it.  Then reboot.  Download the latest version from HP and reinstall it.

If that doesn't help then go in to Windows Update, check for updates then find the HP update and hide it.

 

 

I see some troubling corruption and hard drive problems.

 

Log: 'System' Date/Time: 15/01/2016 12:17:08 PM
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume ??.  The exact nature of the corruption is unknown.  The file system structures need to be scanned online. 

 

 

 
 

 

 

 

Event: 532 Source: ESENT
LiveComm (7696) C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\: A request to read from the file "C:\Users\Amy Martin\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\e4181f4d799caa52\120712-0049\DBStore\livecomm.edb" at offset 2793472 (0x00000000002aa000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

 

 

(If you don't already/ still have Speedfan:  Get it:  http://www.filehippo...nload_speedfan/

 
Download, save and Install it (Win 7 or Vista right click and Run As Admin.) then run it (Win 7 or Vista right click and Run As Admin)  )
In Speedfan, click on the S.M.A.R.T. tab and then on the down arrow to the right of the empty box.  Select your hard drive.  (Only one there on a laptop).  This will show you the info on your hard drive.  It should be all green OKs (or nothing for info only things)  other colors indicate problems.  You can also click on Perform an in depth online analysis of the hard drive   This will open a webpage with more details.  If you right click on "this" at the end of: The link to get back and see a new report about this hard disk in the future is this.
and select Copy Link Address.  You can then paste it (ctrl + v) into a reply and I can look at it too.
 
I would run a disk check on all drives since the error doesn't say which one.
 

a)      Press Windows key + X, select Command prompt (Admin)

b)      At the command prompt, type:

 

 chkdsk [drive:] [/p] | [/r]

 [drive:] Specifies the drive to check.

/p Check even if the drive is not flagged dirty, bad.

 /r Locates bad sectors and recovers readable information (implies /p).

 

Sometimes the Windows Update Troubleshooter will fix things

https://support.micr...te-issues/en-us

 

 

You can uninstall Bonjour.  It's is not working correctly.  It's just a program for Apple stuff.  Unless you have some Apple equipment you don't need it.  You will usually get a new version the next time you upgrade any Apple software.

  • 0

#102
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

http://www.hddstatus...cation=BDED6EFA


  • 0

#103
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts

On the check disk I must be typing in something wrong because it tells me it can't find the path.  How exactly should I type it in?  Also, on the mouse issue.  Bought a new mouse and it's working perfect.  Really bizarre considering the other mouse worked fine on my son's computer.


Edited by A1RotNBrat, 17 January 2016 - 12:00 PM.

  • 0

#104
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,024 posts
  • MVP

OK.  At least one thing is better.

 

chkdsk should work if you use an elevated CMD.  Press Windows key + X, select Command prompt (Admin)  (Note there are two Command Prompt options)  It should start with a prompt C:\Windows\System32: >  which is where chkdsk.exe should live.

 

You can type:

 

dir chkdsk.exe

 

and it should say:

 

 
C:\Windows\System32>dir chkdsk.exe
 Volume in drive C is Windows8_OS
 Volume Serial Number is C66E-CA3C
 
 Directory of C:\Windows\System32
 
10/28/2014  08:26 PM            25,088 chkdsk.exe
               1 File(s)         25,088 bytes
               0 Dir(s)  244,790,960,128 bytes free

  • 0

#105
A1RotNBrat

A1RotNBrat

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 102 posts
Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.
 
C:\WINDOWS\system32>dir chkdsk.exe
 Volume in drive C has no label.
 Volume Serial Number is 5E77-49F2
 
 Directory of C:\WINDOWS\system32
 
10/28/2014  07:26 PM            25,088 chkdsk.exe
               1 File(s)         25,088 bytes
               0 Dir(s)  389,620,273,152 bytes free
 
C:\WINDOWS\system32>

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP