← Back to Knowledge Base

KB #240143: Windows does not start after Encryptionizer installed

⏱️ 3 min read

Type:

Information

Summary:

You have installed Encryptionizer and Windows does not start properly on boot. This article describes how to disable Encryptionizer drivers.

Additional Information:

In very rare circumstances, you may encounter a System Error (“Blue Screen” or “BSOD”), or a black screen where Windows startup appears to be hanging.  We have seen this happen when you install a older version of Encryptionizer not supported on newer operating systems.

Before we can troubleshoot why you experienced the error, you need to disable Encryptionizer drivers in Safe Mode.

To get to Safe Mode use one of these methods:

Method 1: F8 key (availability dependent upon Windows version and Manufacturer)

  • Restart your PC and press F8 repeatedly as soon as you see the Manufacturer logo pop up (and before any Windows logo)
  • Choose SAFE MODE WITH COMMAND PROMPT option and continue to boot.
  • In the command line that is presented, set the Encryptionizer drivers to disabled by running the following 3 commands:
    sc config nlem1402 start=disabled
    sc config nlemsys start=disabled
    sc config nlcbhelp start=disabled
  • Reboot the PC and it should start normally.

Method 2: Windows Automatic Repair with Command prompt

If F8 does not work, you can try to get into the Windows Automatic Repair environment

  • Start up your PC
  • If Windows does not go into the Repair environment on first reboot, you can force it.
    • Power up your machine
    • When the Windows Logo shows on the screen, press and hold the power button to interrupt the boot sequence. Power up again.
    • Repeat the boot interruption two more times and after that it should reach the Automatic Repair environment.
  • Click Advanced Options > Troubleshoot > Advanced Options > Startup Settings.
  • Select Enable Safe Mode with Command Prompt
  • After login, using the command line that is presented, set the Encryptionizer drivers to disabled by running the following 3 commands
    sc config nlem1402 start=disabled
    sc config nlemsys start=disabled
    sc config nlcbhelp start=disabled
  • Reboot the PC and it should start normally.

Once you have been able to successfully restart your PC, work with NetLib Support on the troubleshooting process.

Some Troubleshooting steps: 

Generate a Support Diagnostic Report:

Generate a Memory Dump:

  • In Safe Mode, configure your system to produce a Memory Dump. See this knowledgeBase article for information on how to configure:

KB #240025: How to save and email log files and dump files
https://netlibsecurity.com/kb/kb-240025-save-email-log-files-dump-files/

  • Re-enable Encryptionizer Drivers
    sc config nlem1402 start=system
    sc config nlemsys start=system
    sc config nlcbhelp start=system
  • Restart machine so that new memory dump file is generated.
  • Restart again in Safe Mode and disable Encryptionizer drivers again so that you can access the memory dump file.

Was this article helpful?

Related Articles

KB #240067: Using 3GB Switch in BOOT.INI may cause I/O errors (event ID: 1181)

Type: Information Summary: Using the 3GB switch in boot.ini will severely restrict kernel memory and…

KB #240106: SQL AutoExec script to confirm whether Encryption Key passed to a Secured SQL Instance

Type: Tip Summary: The following script can be used as an “Auto Exec” script inside…

KB #240059: Error: “Invalid path or file name”

Type: Known Issues Summary: When installing API’s or running any Encryptionizer Utility, you receive an…

Still need help?

Our support team is here to assist you.

NetLib Security
AI Assistant · Online
Hi! I'm the NetLib Security assistant. I can answer questions about our encryption solutions, HIPAA compliance, Encryptionizer, and more. How can I help you today?