Changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\SurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.

Fierce GuppyChanging HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\SurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.

...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O

How is a registry value a bug?

Dr_MHow is a registry value a bug?

It is as much a bug as any other software bug. A registry value is just a bug that coincidentally can be fixed by the user as well, something that isn't possible for most bugs hidden from view in the code of a program itself.

It is as much a bug as any other software bug. A registry value is just a bug that coincidentally can be fixed by the user as well, something that isn't possible for most bugs hidden from view in the code of a program itself.

It is not a bug. It simply is a feature that has been implemented due to external GPUs becoming a thing (even if minor). Leaving the registry value set to enable said feature was probably just an oversight of their part.

Breit...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O

Yeah. Supplying a tiny .reg file for download would have sufficed.

Fierce GuppyChanging HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\SurpriseRemovalSupport from 1 to 0 and rebooting also fixes it.

Is that for all nVidia GPUs (internal and external) or just the internal fixed GPUs.

If it's for all, and you don't have an external GPU, simply set the flag and be done with it. If you have an external GPU, however, you still need the 'remove device' capability.

That could explain the size, since the discrimination of internal and external GPUs may have had to be re-thought and implemented in a different way.

Dr_MHow is a registry value a bug?

Take a look at this as an example:

If NVidia decides to put in this in your registry during a Driver Update:

Changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\EnableNukeComputer.ini, and it's in your registry, it becomes active when you log into Windows 10, originally it was set to 0, and they decide to set it to 1 in a patch update in an attempt to blow up your graphic card because they don't like you, you can look at that as being a very bad bug. The end result is NVidia trying to nuke your graphic card in my twisted, hypothetical scenario. On the more realistic side, it's probably more of a software implementation oversight on their end. They added this feature to the recent updates, but they forgot to set it to zero initially. It's caused some issues for consumers who don't understand it's function, used it, and it caused problems. Thus, you have a registry bug of snafu. This is NVidia's way of saying, well, we made a boo boo. Let's fix it.

DethroyIt is not a bug. It simply is a feature that has been implemented due to external GPUs becoming a thing (even if minor). Leaving the registry value set to enable said feature was probably just an oversight of their part.

The oversight was not allowing for morons that thought ejecting the GPU should be done.

Breit...and they need 7 driver versions (.75->.82) and a 300MB download for flipping that bit. o_O

The hotfix being so large is probably because all hotfixes also include the installer for physx, geforce experience, 3d vision etc. Can't explain the huge version jump though lol

Caring1The oversight was not allowing for morons that thought ejecting the GPU should be done.

If you have a high sensitivity mouse and many removable storage devices, misclicking is a legit issue.

Fortunately, it does almost nothing even if you do.