Skip to content
Discussion options

You must be logged in to vote

It would be technically possible from a kernel perspective, but I am not sure we could handle it with the setup packages that we currently use.

The usual manual trick for replacing drivers with new versions is otherwise to rename the driver file in C:\Windows\system32\drivers, copy the new one there and then when rebooting the new version gets loaded instead. Until reboot, the old version stays loaded and stays operational. Other methods are also available such as using sc config command to disable the driver from automatically loading on next reboot and do the actual upgrade then after reboot when the driver is not loaded.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@andreas-eriksson
Comment options

@LTRData
Comment options

Answer selected by andreas-eriksson
@andreas-eriksson
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants