Then it's likely a problem with the passtrough thing Out of curiosity that setup is meant to learn ESX or there is a practical reason to use this setup?
Say thanks to @abbodi1406 who remembered this thread (and also to me that I found a solution ) https://forums.mydigitallife.net/th...hannel-ni_release.85327/page-305#post-1803587
15 days are far from being an extremely late anything, and btw, I didn't look in to it, given was just impossible to do that w/o being affected. I just linked a similar problem that I faced and solved. I was good to find a solution, but you were extremely lucky as there was a chance that I didn't face a similar problem for my entire life, but encountered it just two weeks later.
Does the Nvidia driver version you are referring to (30.0.14.7444) belong to the latest 474.44 Security Update driver for Windows 7? If so, that driver apparently is not WHQL certified due to Microsoft no longer accepting WHQL certification for Windows 7 drivers. So to install this driver may/will require setting the TESTSIGNING setting to ON. Do you have to keep the TESTSIGNING to ON going forward then? I wonder if setting TESTSIGNING back to OFF after successful driver installation will disable the driver again. But it certainly seems strange to me that previous working drivers were disabled after the July 2023 updates. I wonder whether Microsoft did something with the July 2023 updates that we don't know that cause this behavior.
Care to read the rest of the thread. ? The point of 26/07 update is exactly this. Disable previously working drivers..
I updated to august using simplix update pack & I don't have that registry. Noticed after updating to august I can use an old updated driver from 2014. If I update it to the last update which was in 2015. It then says my wifi driver is corrupted & no longer works. It let me uninstall the driver & downgrade back to the 2014 driver but there's no entry for that at all. So I guess I am stuck with the 2014 driver since it works after installing the august update. With July's couldn't even downgrade to the 2014 driver so that's something.
I am sorry, but I still don't understand. This thread is about drivers in Windows 7 being disabled after installing the July 2023 cumulative update. The July 26 update you are referring to is for Windows 11 22H2. Are they related in any way? Unless what you are saying is that the Windows 7 (actually for Windows Server 2008 R2) July 2023 updates also contain the same "functionality", the updated driver revocation list as mentioned in the KB5029033 document? But that document does not mention Windows 7 (which is understandable as Windows 7 should be out of support) and Windows Server 2008 R2 as applicable. So this is really news to me.
So what we can talk only about updates happening in the same day? I guess that if MS decided to blacklist some drivers they did for all the supported OS (or they will do in a short timeframe anyway) I didn't check W7 and the last nvidia VGA that entered in my house was a Riva 128 in '90 or so. That said I provided all the relevant infos in the thread I linked, including where to look in the event-viewer. In short I did way much than I had to do about a problem happened to something I don't use. It's up to YOU and eventually to other affected people to understand if it's the same problem or it's a completely unrelated problem. I'm an expert and a tecnician, but I'm not a wizard. I can do educated guesses, but still I don't have any pallantir in my tool box
are u sure that it does work on 7? by default this registry entry does not exist .i added it manually. will it work? i now get an error 39 when im trying to install a 2014 driver for my wifi ( PCI\VEN_1814&DEV_3090&SUBSYS_1453103C&REV_00 )
Just read the message above. NO Death and taxes are the only sure thing of this world. Whatever I stated clearly where to look to understand if the problem is the blacklist
it seems that the registry entry does not work.i put it manually then tried to install a newer driver for my wifi card and i get the error 39 (driver missing or corrupted) before the july updates it worked.i hope someone a workaround..
Yeah from what I am guessing this is a fix on more modern windows. Because I checked out windows 10 ltsc & the registry is there. So no idea what’s up with windows 7 there’s a chance they are blocking drivers with another method I guess & I mean that’s what I assume the reason is & why there isn’t a registry. Also no idea if the registry is there on windows 8.1 but it’s there on windows 10 ltsc
@acer-5100, I think that part of the recent confusion in this thread is that this thread was forked from the Simplix thread, and was and still is, in the Windows 7 sub-forum. [I'm not sure why it was forked without maintaining the Simplix references.] The references to the July 2023 update in the thread title, and in the early posts, all referred to the July 2023 update of Simplix. It seems that your posts do not refer to Windows 7, and more specifically do not refer to Simplix, since you admit that you have never used the app, and the July update you refer to is an update to Windows 11, as @James Bond 007, pointed out. While I totally agree with you that some problems and solutions for one OS can apply to other OS, it seems that in this case they don't, though the problems are related. I totally understand that it is always up to the reader to determine for themselves if a given solution applies to them, this Windows 10+ solution is really causing confusion in this Windows 7 thread, as the readers would sincerely love to find such a simple, effective solution. The readers, including myself, leaped to an incorrect interpretation of your comment: Would it be possible to please edit your post to reinforce that, while related to this thread, your solution does not apply to Windows 7? TIA