Hey guys!

I had to restart my PC yesterday using the power button after I ran into an issue with the USB controller suddenly stopped working resulting in no keyboard nor mouse. I managed to RDP into the PC from my mobile phone and thought I was able to restart my PC successfully. But the screen never came on again after the reboot showing 'No signal'. So, in the end I had to shut it down by holding the physical power button depressed for a couple of seconds.

After this all seemed good and Windows started up just fine with no issues. Still, I figured it might be a good idea to check my disks as well as running SFC to make sure I didn't end up with any corrupt files as a result of the "hard" shutdown.

No disk issues found but running sfc /scannow informed me corrupt files were found that couldn't be fixed. I then tried dism /Online /Cleanup-Image /RestoreHealth as well as dism /Online /Cleanup-Image /RestoreHealth /Source:wim:L:\sources\install.wim:1 with and without the /limitaccess switch but still no go. Ended at about 90% throwing error 3017 telling me the requested operation failed and that a system reboot was required to roll back changes made.

Someone suggested in another forum I should try a Windows repair downloading and using the most recent ISO. So I did and the repair finished successfully but the exact same problem remains even after the repair.

Here's CBS.log as well as dism.log. What I found most interesting in the logs are a couple of lines in CBS.log referring to a file called storport.sys. Not really sure though what devices is actually using that file. I learned it's some kind of standard Microsoft storage driver but going through all my storage devices in Device Manager, I haven't been able to find a single one using this specific file/driver.

Here's the lines of most interest in CBS.log I think.

2018-09-27 03:32:06, Info CSI 00003385 Hashes for file member [l:12]'storport.sys' do not match. Expected: {l:32 b:163423f1d9ab4271ee997536a78b2d7b0472a15c1a45c608b0a0fed49fc6ed3c}. Actual: {l:32 b:aa7b4cda0cf8a3ff42c4d438612d32d69b2a249811eb91beed734b295355edfb}.

2018-09-27 03:32:06, Info CSI 00003386 [SR] Cannot repair member file [l:12]'storport.sys' of Microsoft-Windows-StorPort, version 10.0.17134.137, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2018-09-27 03:32:06, Info CSI 00003387 [SR] This component was referenced by [l:80]'Package_1037_for_KB4458469~31bf3856ad364e35~amd64~~10.0.2.2.4458469-2210_neutral'

2018-09-27 03:32:06, Info CSI 00003388 Hashes for file member [l:12]'storport.sys' do not match. Expected: {l:32 ml:4096 b:163423f1d9ab4271ee997536a78b2d7b0472a15c1a45c608b0a0fed49fc6ed3c}. Actual: {l:32 b:aa7b4cda0cf8a3ff42c4d438612d32d69b2a249811eb91beed734b295355edfb}.

2018-09-27 03:32:06, Info CSI 00003389 Hashes for file member [l:12]'storport.sys' do not match. Expected: {l:32 ml:4096 b:163423f1d9ab4271ee997536a78b2d7b0472a15c1a45c608b0a0fed49fc6ed3c}. Actual: {l:32 b:aa7b4cda0cf8a3ff42c4d438612d32d69b2a249811eb91beed734b295355edfb}.

2018-09-27 03:32:06, Info CSI 0000338a [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\Drivers\\storport.sys; source file in store is also corrupted

I'm on Win 10 1803 Build 17134.320 with all the latest MS fixes applied as of today.

Edited to add one thing I forgot to mention. Booting into safe mode, SFC doesn't report any issues. It will only fail when booting Windows into normal mode.

Many thanks in advance for any tips on how to sort this one!

Edited September 27, 20187 yr by WebMaximus
Added some info

An odd fix but I've seen this mentioned a few times:

 

I've done multiple restarts, even formatted the drive and done a clean Windows install to try and eliminate driver issues... however I found a thread online where someone in comments mentioned in passing they'd gone into Sleep mode, then woken the PC up and that cleared it.

And... it did. Somehow my computer has carried a broken Power setting through multiple installs of Windows...? But I can't see how, unless something went wrong with the BIOS, or maybe there's a loose wire in the case somewhere?

It was recommended I reset the power configurations, which I did via CMD.

1.) Click Search
2.) Type CMD
3.) Right click "Command Prompt" and select "Run as Administrator"
4.) Copy and paste "powercfg -restoredefaultschemes" and hit enter.

And now, I've got full performance back again! As I say, weird...

 

Alternatively, you could try this:

https://www.drivereasy.com/knowledge/storport-sys-in-windows-10-try-these-steps/

Very happy to report I finally managed to sort this issue and sure enough storport.sys was the culprit!

I actually had 3 copies of that file where one of them was considerably smaller than the other 2 copies. Still, the company in the details of the file was Microsoft Corporation. So it did appear like a valid copy of the file. The smallest file was 34.6 kB wheras the other two copies of the file were 548 kB each.

Anyways, after some hassle taking ownership of the smallest file and the folder where it was located I was able to replace it with a copy of the storport.sys file located in %windir%\System32\Drivers.

I then rebooted my PC and ran SFC followed by DISM and what do you know...both of them now finished successfully! I finished off by resetting the owner of both the folder and the new copy of the file back to TrustedInstaller.