• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

PSA: "NVIDIA Installer cannot continue" on Windows October 2018 Update and How To Fix It

Microsoft could fix it all by just asking after each update if you would like to have Win10 auto download drivers or if you want to configure yourself. But then we would be given choices and we all know how hard choices are.
 
By dinossaur you mean the graphic appearance? If so I can understand, but I don´t judge OS by their visual! I judge it by stability. Windows 7 use your CPU smarter than Windows 10, not to mention RAM management. The input lag on Windows 7 is lower too, and the mouse translation too. It runs with less 200 services background and it doesn´t work by modules like Windows 10. It is a superior OS compared to Windows 10, but it lacks Directx12 and the visual effects. That´s all. There isn´t a single advantage on Windows 10 compared to Windows 7 OS wise.

The only true statement in that post is that Win7 lacks DX12.
 
By dinossaur you mean the graphic appearance? If so I can understand, but I don´t judge OS by their visual! I judge it by stability. Windows 7 use your CPU smarter than Windows 10, not to mention RAM management. The input lag on Windows 7 is lower too, and the mouse translation too. It runs with less 200 services background and it doesn´t work by modules like Windows 10. It is a superior OS compared to Windows 10, but it lacks Directx12 and the visual effects. That´s all. There isn´t a single advantage on Windows 10 compared to Windows 7 OS wise.

No, I mean a dinosaur on how it functions. Things like the much more functional Task Manager, the much better file transfer window, the much improved multi-monitor support, just to name a few.

I don't agree that Windows 7 uses the CPU better at all, and RAM management also isn't any better with Windows 7. Windows 7 uses less RAM at idle, but do I really care? No, it really makes no difference if you have 4GB or more.
 
Unrelated, but I recently updated drivers and I had to block nvidia at least 4 times in my firewall. Assholes kept trying to get internet access with every EXE they have.
 
Unrelated, but I recently updated drivers and I had to block nvidia at least 4 times in my firewall. Assholes kept trying to get internet access with every EXE they have.

I made a post about pi hole in a guide here https://www.techpowerup.com/forums/threads/guide-global-network-dns-blacklisting-pi-hole.233545/

I also follow the community on reddit. This was a post about the GFE (Geforce experience) legit 2 days ago.


rediculous
 
All these people having issues with 1809. Installed/updated all 6 of my system. Not a single issues....who are these folks? 2 of my system which are gaming rigs both Nvidia.......Nada single hick up.......Again who are these folks?

Just because you say you aren't doesn't mean others are not having problems. If they weren't this thread would not exist!
 
more like using that cloud based malware service called windows 10 . [lol...] so are folks with real operating systems having this issue ? [win-7 / Linux ]

This issue only occurs with Windows 10, because Universal Windows Drivers are not available on any other version.
 
This issue only occurs with Windows 10, because Universal Windows Drivers are not available on any other version.

They were named differently.

https://www.sevenforums.com/tutorials/2803-device-installation-settings.html
Win 7 would automatically do it by default. When tweaking an OS that is the first setting to get turned off

Unrelated, but I recently updated drivers and I had to block nvidia at least 4 times in my firewall. Assholes kept trying to get internet access with every EXE they have.

Check task scheduler
 
The uwd driver gets added to driver store and will install even without network.

Idk about that. I just did a fresh install 2 weeks ago with the latest iso. from Microsoft for Windows 10. I always do my network drivers last after installing all the major drivers (motherboard, video card, sound card, & nvme drivers). I never had an issue with this at all with all the fresh windows setups I've done in the past and present.

One thing I don't do is log in with my email account to activate windows 10. I always have a key code
 
This! Windows 10 is one of the worst Windows imo, but people are using it as microsoft basically "forced" upgrades for free. The OS is terrible. Windows 7 is smoother and has more stability.

BS.
 
They were named differently.

https://www.sevenforums.com/tutorials/2803-device-installation-settings.html
Win 7 would automatically do it by default. When tweaking an OS that is the first setting to get turned off

That is different than UWD. That is just Windows installing a standard driver that it downloads from Windows Update.

Universal Windows Drivers are actually a different type of driver that uses the Windows App Store system to install the driver. From my understanding it is kind of like the difference between a normal desktop program, and an App that you'd get through the Windows App Store.

This is why there is an issue when trying to install the normal driver when the UWD has already been installed. The normal driver doesn't know how to handle the UWD already being there. This is more of an nVidia issue, IMO, than a Microsoft one. Their driver should know how to handle a UWD already being installed.
 
That is different than UWD. That is just Windows installing a standard driver that it downloads from Windows Update.

Universal Windows Drivers are actually a different type of driver that uses the Windows App Store system to install the driver. From my understanding it is kind of like the difference between a normal desktop program, and an App that you'd get through the Windows App Store.

This is why there is an issue when trying to install the normal driver when the UWD has already been installed. The normal driver doesn't know how to handle the UWD already being there. This is more of an nVidia issue, IMO, than a Microsoft one. Their driver should know how to handle a UWD already being installed.

Thats an evolution step of what I specified- provides basic functionality, not optimized...


Command calls encoded are lacking from NV then. If ms would stop with the mucking of the wddm platform every build then maybe the gpu makers wouldn't have these problems and having to guess all the friggin time, yet another reason to refuse W10, you think after 1 year the OS would be right...
 
So it shows Microsoft doesn't care anymore and for the money NVidia charges 4 their products, drivers support is subpar. No communications btw those 2 companies. Things are going bad. I have witnessed that with Intel hardware too. Except Intel reacts and fixes their issues much faster and smoother.
 
Idk about that. I just did a fresh install 2 weeks ago with the latest iso. from Microsoft for Windows 10. I always do my network drivers last after installing all the major drivers (motherboard, video card, sound card, & nvme drivers). I never had an issue with this at all with all the fresh windows setups I've done in the past and present.

One thing I don't do is log in with my email account to activate windows 10. I always have a key code
Not using a MS account either, I even say "i don't have a key" during the usb install to save on time, I can paste the key later through remote desktop.

Doesn't W10 come with drivers for your NIC? If it doesn't and you install NIC drivers last, then you're basically doing the first method we listed in the article. For (most?) systems the NIC driver is already included and Windows will start searching for a graphics driver from Windows update as soon as network connectivity is found (within a minute or so, I tested this on a fresh install yday).
 
Moral of the day: Never leave updates to MS or Windows in auto-pilot. ALWAYS go for manual, incremental updates whenever possible. Tons of hassle but less trouble in the long run.
 
No just firing it off. Windows is probably locking it because of rollback and its using the installed service DB.
This seems to be just a timing issue. afaik the driver gets removed, which marks the driver as deleted. Once the driver has fully stopped the driver can actually be deleted, which stops the nvlddmkm service. You firing off commands so quickly will just mark the nvlddmkm service itself as deleted, which doesn't remove the DCHUVen key, so NV installer still thinks it's running on DCH. Try removing that registry key manually in your script
 
Last edited:
When Intel does transition to DCH last weeks - "wow superb driver" etc, and when Nvidia doing that - "buuuu we want older drivers"... wtf??? Really don't understand...
Maybe because you can't found DCH installers, Yes, that Nvidia screwed up, you can found direct links to DCH drivers on their forums or just use - like me - Nvidia Experience
Also DCH was introduced in Redstone 3 ie. 1709 not 1809 - it only spread more now because OEM require to use them, in 1709 and 1803 DCH was optional.
I use DCH for Realtek HDA too - new modern control panel is great, also DCH driver is like 30MB vs standard 250MB.
 
By dinossaur you mean the graphic appearance? If so I can understand, but I don´t judge OS by their visual! I judge it by stability. Windows 7 use your CPU smarter than Windows 10, not to mention RAM management. The input lag on Windows 7 is lower too, and the mouse translation too. It runs with less 200 services background and it doesn´t work by modules like Windows 10. It is a superior OS compared to Windows 10, but it lacks Directx12 and the visual effects. That´s all. There isn´t a single advantage on Windows 10 compared to Windows 7 OS wise.

You need to stop pulling 'facts' out of your arse. 70% of what you're writing needs a source or it only happens in your imaginary 240hz world. Input lag, mouse translation, RAM management... its a load of nonsense. As for stability, Windows 7 is evidently less stable and lockups will force far more reboots than on 10, so that is already crossed off. The rest... waiting for that source.

Regardless... isn't this issue easily fixed with Geforce Experience? You can easily uninstall it afterwards. Windows Driver > GFE update > uninstall GFE > Maybe even get a separate Geforce driver from the website if you feel the need. That then also eliminates the telemetry concerns.
 
Regardless... isn't this issue easily fixed with Geforce Experience? You can easily uninstall it afterwards. Windows Driver > GFE update > uninstall GFE > Maybe even get a separate Geforce driver from the website if you feel the need. That then also eliminates the telemetry concerns.
You have to register, login, at which point telemetry gets uploaded, then you can update the driver. And for the next driver update you'll need GFE again because you're stuck on DCH drivers
 
There is no true statement in your post at all.



You need to put source too, about what you said. In fact forums are useless because only what Vayra86 says is valid. If any other user posts something he needs source.

I hope you are not from 1986, otherwise I would seriously think about my life by being 24/7 arguing with ppl on the internet forums, at 32 years old. Cringy.
That is a pointless attack based upon age there.
 
This seems to be just a timing issue. afaik the driver gets removed, which marks the driver as deleted. Once the driver has fully stopped the driver can actually be deleted, which stops the nvlddmkm service. You firing off commands so quickly will just mark the nvlddmkm service itself as deleted, which doesn't remove the DCHUVen key, so NV installer still thinks it's running on DCH. Try removing that registry key manually in your script

Actually thats the first thing I do.

Remove reg key

Remove inf

Delete Service.

I followed the order of the OP.

I added a timeout between removing the INF and deleting the service this time.
 
Last edited:
That is a pointless attack based upon age there.

Nothing compared to his daily or should I say hourly attacks he makes on everyone on every tech power up news article, if you notice. The dude is here everyday quoting other users posts and going against it. Just check his activity and recent posts. Beefs on every topic. He is known on other forums, yeah it reached that point.

Is not an attack based upon age. Simply put if you are 32 y old and all you do the whole day is arguing with other people on TpU forums, you surely need to check your priorities. Nothing wrong with being 32 y old. Is what you do that is wrong. This dude is very toxic and spreads toxicity on every damn thread, constantly forcing his opinions and point of views on other people that disagree with him. How pathetic it is that you are 30+ and do such a thing 24/7 on the web? Please...
 
Last edited:
Nothing compared to his daily or should I say hourly attacks he makes on everyone on every tech power up news article, if you notice. The dude is here everyday quoting other users posts and going against it. Just check his activity and recent posts. Beefs on every topic. He is known on other forums, yeah it reached that point.

Is not an attack based upon age. Simply put if you are 32 y old and all you do the whole day is arguing with other people on TpU forums, you surely need to check your priorities. Nothing wrong with being 32 y old. Is what you do that is wrong. This dude is very toxic and spreads toxicity on every damn thread, constantly forcing his opinions and point of views on other people that disagree with him. How pathetic it is that you are 30+ and do such a thing 24/7 on the web? Please...

Well instead of arguing yourself report it or ignore him.
 
You have to register, login, at which point telemetry gets uploaded, then you can update the driver. And for the next driver update you'll need GFE again because you're stuck on DCH drivers
Not really a problem. Having GFE is the easiest way to ensure that MS Never tried to update the Nvidia driver. You can completely control GFE doing it by just saying no.
 
Not really a problem. Having GFE is the easiest way to ensure that MS Never tried to update the Nvidia driver. You can completely control GFE doing it by just saying no.

Gfe had side effects for some users, so this is a losing battle at this point. MS got too greedy when they stopped users from upgrading just directX
 
Back
Top