Windows 10 V1803: HCVI causes driver error code 39

[German]Users of Windows 10 may experience a nasty surprise when switching to version 1803. Drivers are no longer be loaded and return the error code 39 in the device manager – although all worked before installing the feature update. This is due to Core Isolation (HCVI), which was implemented in all versions of Windows 10 since version 1803 – and can cause the driver error on compatible machines.


The error

The error, that users are facing in Windows 10 V1803 is always the same. The driver suddenly cannot be loaded. Here is the message

Windows cannot load the device driver for this hardware. The driver may be corrupt or missing. (Code 39)

{Invalid image}

%hs is either not intended to run under Windows or contains an error. Reinstall the program using the original installation media or contact your system administrator or software vendor for assistance. Error status 0x

Within this German MS Answers forum post it has drastic consequences. After installing the feature update lifting the machine to Windows 10 V1803, the Intel(R) HD Graphics 3000 and its drivers no longer works. The Microsoft Basic Display Driver takes over the screen output, but only supports a resolution of 1024 x 768 pixels.

The root cause: Core isolation

Error code 39 indicates an incompatible or damaged driver. But with Windows 10 April Update there is an additional problem, which my German colleague Ingo Böttcher described in his German blog post here. Microsoft has also introduced the so-called core isolation (HVCI) in the home versions of Windows 10 V1803 (previously this was limited to the Device Guard of the Enterprise Edition, see).

HVCI isolates the kernel via the built-in hypervisor (virtualization) to protect it. However, hardware support is needed. As Ingo writes, apart from Virtualbox issues also various drivers have problems with the new HVCI featrue. However, you can control and turn off core isolation on supported machines in the Windows Defender Security Center. Within this article is a screenshot and an explanation how to turn it on – this feature isn#t supported on my test system's hardware.

A bug prevents disabling HVCI in GUI

In Windows 10 version 1803, however, there is a bug that to my knowledge was not fixed until June 2018. Once an HVCI function has been activated, it can no longer be switched off via the Windows Defender Security Center (see this post). The workaround is to invoke the registry editor via Run as administrator and then navigate to the key:



Then set the DWORD value Enabled to 0 (see also this Microsoft article) and reboot Windows 10. After that HVCI should be disabled and the old drivers (or Virtualbox) should work again.

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Windows and tagged , , , , . Bookmark the permalink.

15 Responses to Windows 10 V1803: HCVI causes driver error code 39

  1. Yash says:

    Thanks for this . It worked.

  2. Em says:

    Thanks ever so much for this.

    I have been struggling for two days to find a solution as to why my intel hd graphics driver suddenly stopped working. There was a yellow warning in device manager and a code 39 for the display drivers. Max screen resolution with windows basic display driver was only 1600 x 1200 instead of 1920 x 1080 making text look distorted.

    Tried reinstalling the drivers with no success.

    Luckily I came across your article and it worked a treat.

  3. Sam says:

    Doesn't seem to work on the latest inside (18309)…. the key itself seems to have moved however neither toggling the new nor old seems to be doing it for me :(

  4. Advertising

  5. Clement Oke says:

    After trying to find a fix for my driver issue, I came across your article and I turned off Core Isolation, rebooted and everything works fine now. I was previously suspecting the Special Folder Access settings and I turned it off to no effect. I even downloaded the 1809 update and I couldn't install it, and I believe it must have been the work of the Core Isolation Settings.

  6. Lassi U says:

    Thanks! That helped in my Acer 5951G laptop. It also had DVD-rom missing with code 39.

    Happy happy happy!

  7. Thomas says:

    Has anyone found a way to have drivers working with core isolation turned on ? I bought a webcam, but I keep finding error 39 while core isolation is on. I really would like to leave it turned on, as it increases security mainly against rootkits.

  8. W10-User says:

    We have been seeing this problem since 2017 and Windows 10 version 1607 LTSB (Enterprise) when Device Guard was enabled. Unfortunately, the affected manufacturers (e.g. Huawei for LTE modem E3372h-153) would have to update their drivers accordingly. Unfortunately there is not much happening. Obviously there is little interest in it.

  9. Peter Seidel says:


    Nach dem Upgrade auf Windows 10 1909 und dem Aktivieren/Installieren einiger "Windows Features" ging die Webcam mit "Code 39" nicht mehr.

  10. Leonard says:

    Thank so much I've struggled with graphics 3000 display drivers for almost 3 days now then stumbled on this and it worked!!

  11. Kieran says:

    Thanks, this worked for me.

  12. Arian van der Pijl says:

    Happens also with the inbox / WU drivers for a Logitech C270 webcam.
    You can change the driver to the Windows generic 'USB Video Device' driver.

  13. Andy D says:

    Hi Guenni,

    Many thanks to you and all the people who spend countless hours researching the root cause of issues that can make or break the day for computer users.
    Much appreciate you sharing the post.

    Had turned on Application Guard to get my Hyper-V working again on Windows 10 which seem to break my display drivers and checkpoint VPN connectivity.

    It took me a day of not doing some serious damage to my PC to try and troubleshoot various ways of getting my display driver to work.

    Your article was a sign of relief which worked like a charm.

    Many thanks with much appreciation and gratitude to your work.
    Happy to subscribe to your articles.

  14. Dennis Foreman says:

    Your tip fixed my C270 camera same as for other people. I have not tested the camera's audio, but had to do essentially the same thing. Thanks!!

  15. Jig says:

    It worked. Unfortunately every few days I have to do it again.

Leave a Reply

Your email address will not be published. Required fields are marked *