Can only boot with disabled driver signature enforcement after crash

Page 1 of 2 12 LastLast
  1.    19 Feb 2018 #1

    Can only boot with disabled driver signature enforcement after crash


    Hi,

    I am running Windows 10 Enterprise Edition on an Acer notebook.
    Yesterday there was a short power outage, for about 5 seconds, which crashed my computer. After that I couldn't boot normally into Windows anymore. The computer just stays stuck at the Acer logo, even when trying to boot in safe mode.

    So, I tried various things from the Windows Automatic Repair menu and the console I could access through that.
    But nothing I did there helped.

    After all that I tried out all the options in the Startup Settings and with #7 Disable driver signature enforcement I can actually get into Windows again.
    When I boot like that, it seems to boot rather slowly though.


    I ran sigverif and that shows 2 files that haven't been signed.

    - basicrenderer.sys version: 10.0.16299.19
    - bthport.sys version: 10.0.16299.64


    - How can I fix that and sign these drivers? I don't want to run the computer with that permanently disabled.
    - And are these 2 files not being signed even the actual reason for me not being able to boot Windows?
    - Is it possible that that happened when my computer suddenly crashed?


    I also ran sfc /scannow and that returned:

    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

    I was then looking into CBS.log to find that, but that file has 37492 lines and I don't know what to search for.

    - Is that also related to the startup issue?
    - How can I find which corrupted files it hasn't been able to fix?


    I also had a look into SRTlog and it says there:
    - Number of root causes = 1
    - all the error codes are 0x0
    - Startup Repair has tried several times but still cannot determine the cause of the problem.

    - What is that telling me about the problem?
      My ComputerSystem Spec

  2.    19 Feb 2018 #2

    Signed driver is one that has been submitted to ms who test to ensure they won't mess up windows. Windows enforces this so it won't boot those none signed drivers. You need to remove them or find signed drivers
      My ComputerSystem Spec

  3.    19 Feb 2018 #3

    Please execute below commands one at a time:

    Code:
    Dism /Online /Cleanup-Image /RestoreHealth
    
    Sfc  /Scannow
    Make sure you are connected to internet when you are executing Dism command as it will replace damage system files with downloaded system files from Microsoft.
      My ComputerSystem Spec

  4.    19 Feb 2018 #4

    Indeed, I would have recommended what FreeBooter already did. If everything worked before the outage, the reason for this change is very likely to be corruption of the drivers that now show up as unsigned. Chances are decent (but by no means 100%) that the DISM repair will find and replace those drivers. OTOH, if it doesn't work you may have no choice but to (a) roll in your most recent backup or (b) if you don't have a recent backup, you may very well have to resinstall. Because the chance of (b) is non-zero, you should boot your Acer using the Macrium Reflect "rescue media" and make a backup of your system (so you can return to it later to extract files or other information you might need) right away.
    HTH,
    --Ed--
      My ComputersSystem Spec

  5.    21 Feb 2018 #5

    OK, I did that. But the drivers are still unsigned and I get the following messages when running

    Dism /Online /Cleanup-Image /RestoreHealth and Sfc /Scannow.



    dism gives me this result:

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.15

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.



    and sfc says:

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.
      My ComputerSystem Spec

  6.    21 Feb 2018 #6

    Did you execute Dism command after Sfc command finish executing?

    Do you have Windows 10 Installation DVD if not can you download the Windows 10 ISO image using Media Creation Tool?


    Please open the Command Prompt by typing cmd.exe into Start Menu, right-click on Cmd.exe, and open it as an administrator.

    Type following command and press Enter key.

    Code:
    Findstr  /c:"[SR]" %SystemRoot%\Logs\CBS\CBS.log  > %UserProfile%\Desktop\Cbs.txt
    Please attached the Cbs.txt file stored at the Desktop to your next post.
      My ComputerSystem Spec

  7.    21 Feb 2018 #7

    Having the same issue with about 6 different computers. Some Windows 10 home some Windows 10 pro. Disabling the driver signature enforcement will allow Windows to load.

    Performing a system restore to a few days prior will also work. Running Windows update appears to break it again. It tried to install 2018-02 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4074588) but fails with - Error 0x80070002.


    Same with KB4074588 with - Error 0x80240034


    I also see the two unsigned drivers
    -basicrenderer.sys version: 10.0.16299.19
    -bthport.sys version: 10.0.16299.64



    We are using Labtech as well to patch computers.



    We have also upgraded any of the ones that are currently Pro from Home. But there are a few that are still Home that are having this issue.

    We have several clients with hundreds of computers each and this issue is only happening at this one location.

    I am trying the steps in this thread now.
      My ComputerSystem Spec

  8.    22 Feb 2018 #8

    Please let us know how this turns out. Lots of people (and businesses) are dealing with the same issues.
    Thanks!
    --Ed--
      My ComputersSystem Spec

  9.    22 Feb 2018 #9

    I did a system restore again. Rebooted several times successfully. Those two unsigned drivers were still on there. So it seems that those are not the issue. Then I ran Windows updates again. It failed the 2018-02 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4074588) still. It also installed the (KB890830) Windows Malicious Software Removal Tool x64 - February 2018. It appears that all of the machines have installed this and failed on the other.
      My ComputerSystem Spec

  10.    24 Feb 2018 #10

    FreeBooter said: View Post
    Did you execute Dism command after Sfc command finish executing?

    Do you have Windows 10 Installation DVD if not can you download the Windows 10 ISO image using Media Creation Tool?


    Please open the Command Prompt by typing cmd.exe into Start Menu, right-click on Cmd.exe, and open it as an administrator.

    Type following command and press Enter key.

    Code:
    Findstr  /c:"[SR]" %SystemRoot%\Logs\CBS\CBS.log  > %UserProfile%\Desktop\Cbs.txt
    Please attached the Cbs.txt file stored at the Desktop to your next post.

    Hello,

    sorry for the late response, but I didn't receive any notification emails about answers here (I got them for the first few replies), so I didn't think anyone posted here...
    I ran DISM before and after sfc. I ran both of them a couple of times.
    I do have a Windows 10 installation DVD.

    The cbs.txt file contains the following lines:
    2018-02-25 09:54:48, Info CSI 00000006 [SR] Verifying 1 components
    2018-02-25 09:54:48, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
    2018-02-25 09:54:48, Info CSI 0000000b [SR] Verify complete
    2018-02-25 09:54:48, Info CSI 0000000c [SR] Verifying 1 components
    2018-02-25 09:54:48, Info CSI 0000000d [SR] Beginning Verify and Repair transaction
    2018-02-25 09:54:48, Info CSI 0000000f [SR] Verify complete
    2018-02-25 09:54:48, Info CSI 00000010 [SR] Verifying 1 components
    2018-02-25 09:54:48, Info CSI 00000011 [SR] Beginning Verify and Repair transaction
    2018-02-25 09:54:49, Info CSI 00000015 [SR] Verify complete
    2018-02-25 09:54:49, Info CSI 00000016 [SR] Verifying 1 components
    2018-02-25 09:54:49, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
    2018-02-25 09:54:49, Info CSI 0000001b [SR] Verify complete
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
I've just bought a laptop with Windows 10 and a couple of days in I have a problem. It won't startup unless I select the "Disable Driver Signature Enforcement" option. I have used sigverif to see what drivers I have unsigned. I was surprised to...
Hi! I have purchased two licenses of Windows 10 Pro x64. Everything works fine, except for one disturbing elements. I have an unsigned driver to a program that I use every day, so I have to boot in the "Disable Driver Signature Enforcement"...
So this is my 14th or 15th time attempting to disable the driver signature enforcement so I can use motioninjoy to install my PS3 Controller driver to use for Rocket League. However, every time I run advanced startup, the process goes rather slowly...
Driver signature enforcement in Drivers and Hardware
I used option 7, on troubleshooting startup, to disable driver signature enforcement and allow me to install an Argyll CMS driver for an i1 spectrophotometer. Do I have to re-enable signature enforcement or will it come back on at the next...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:13.
Find Us