Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Boot problem please help


  • Please log in to reply
2 replies to this topic

#1 Flokeeh

Flokeeh

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:37 AM

Posted 25 July 2016 - 09:38 PM

Recently i used the following cmd command bcdedit /deletevalue nointegritychecks and now im experiencing boot issues

 

Automatic PC startup repair can't fix this

 

I tried safe mode but PC wont start up without disabled driver signature enforcement mode

 

please help me

 

BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,714 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:12:37 AM

Posted 27 July 2016 - 08:33 AM

What prompted you to run this command?

 

If you are able to boot into Windows do a system restore using a restore point dated prior to using this command.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 CKing123

CKing123

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:British Columbia, Canada
  • Local time:12:37 AM

Posted 03 August 2016 - 04:11 PM

The command that you ran bcdedit /deletevalue nointegritychecks enables driver signature enforcement. If it was disabled before, then that could be the cause of the problem. Like @dc3 said, why did you run this command? You can always turn it back on, although its not recommended. I suggest that you use the disable driver enforcement mode to boot up, and then see which driver is causing the problem

 

-CKing


If I am helping you and I don't respond within 2 days, feel free to send me a PM

Sysnative Windows Update Senior Analyst 

Github | Keybase





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users