Windows takes two hours to boot every reboot. Goes to spinning circles

What do you have attached to the computer? I keep seeing a PNP device error in a couple of places and a Windows Update Failure.

Code:

Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0
 
Problem signature:
P1: 10.0.10586.162
P2: 80240438
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 0
P8: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P9: {7971F918-A847-4430-9279-4A52D1EFE18D}
P10: 0
 

+++ WER1 +++:
Fault bucket , type 0
Event Name: PnPDeviceProblemCode
Response: Not available
Cab Id: 0
 
Problem signature:
P1: x64
P2: Sensors\SensorsSimulatorDriver
P3: {5175d334-c371-4806-b3ba-71fd53c9258d}
P4: 0000001F
P5: WUDFRd.sys
P6: 10.0.10586.0
P7: 10-30-2015
P8: 
P9: 
P10:

RobH2 said:

CHKDSK finished with no errors. I ran it in 'read-only' mode as I was working on something. i hope that a "no error" report is still valid from 'read-only.' If not I can finish what I'm doing and run it again using '/F'.

Windows has scanned the file system and found no problems.
No further action is required.


116639743 KB total disk space.
66337540 KB in 329491 files.
263508 KB in 76955 indexes.
0 KB in bad sectors.
1449083 KB in use by the system.
65536 KB occupied by the log file.
48589612 KB available on disk.


4096 bytes in each allocation unit.
29159935 total allocation units on disk.
12147403 allocation units available on disk.

OldMike65 said:

Most of the time running chkdsk SHOULD reboot computer and THEN it runs .... not sure just how reliable your method was.
chkdsk c: /f should have been tried. But, simrick is checking on your errors.

He ran it in read-only mode - it won't reboot because it's not fixing anything. It's fine.

Do you have a wired keyboard and mouse? If so attach them, remove all items wireless and everything else, such as the Wacom Tablet and Hard drive, USB hubs and the Space Pilot. In other words everything except the wired keyboard and mouse. Then Reboot. Be sure to remove the wireless dongle too.

RobH2 said:

When you say "this" do you mean was I able to see it running in a command window? Yes.

Yes, that's what I meant.

Code:

2016-03-31 12:33:31, Info                  DISM   DISM Package Manager: PID=15896 TID=15912  Error in operation: (null) (CBS HRESULT=0x80070570) - CCbsConUIHandler::Error
2016-03-31 12:33:31, Error                 DISM   DISM Package Manager: PID=15896 TID=15916 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070570)
2016-03-31 12:33:31, Error                 DISM   DISM Package Manager: PID=15896 TID=15916 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070570)
2016-03-31 12:33:31, Error                 DISM   DISM Package Manager: PID=15896 TID=15916 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070570)
2016-03-31 12:33:31, Error                 DISM   DISM Package Manager: PID=15896 TID=15916 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070570)
2016-03-31 12:33:31, Info                  DISM   DISM Package Manager: PID=15896 TID=15916 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-03-31 12:33:31, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070570
2016-03-31 12:33:31, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070570

How old is that ISO?; have we gone through windows updates since it was downloaded? If so, we need a current ISO.