[DISCUSSION] Code 52 error on multiple device drivers after July 2023 update

Discussion in 'Windows 7' started by johnnypop, Jul 15, 2023.

  1. johnnypop

    johnnypop MDL Novice

    Feb 11, 2012
    4
    1
    0
    Anyone having problems with july pack "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
    My nvidia driver (Orginal from nvidia) won't start unless I disable driver signature enforcment
     
  2. ExiledRose6084

    ExiledRose6084 MDL Junior Member

    Apr 14, 2023
    98
    53
    0
  3. johnnypop

    johnnypop MDL Novice

    Feb 11, 2012
    4
    1
    0
    Yeah strange that the drivers that did work fine before do not work now.
    It's not like they are modded, they are from the manufacturer.
    So the only option is F8 and disable driver signature enforcement?
    Is that Microsoft trying to turn people off Windows 7 I guess...
     
  4. ExiledRose6084

    ExiledRose6084 MDL Junior Member

    Apr 14, 2023
    98
    53
    0
    #5 ExiledRose6084, Jul 16, 2023
    Last edited: Jul 16, 2023
    Maybe but eh like I said in my post experienced this on other windows so kind of doubt it.

    Anyway you can still download the last simplix update pack (junes) from the mega link for now.

    So I did a clean install, downloaded & installed junes simplix update pack, & all works fine.

    So if your going to do a clean install recommend grabbing it from the mega link before it gets updated to July.

    Then for turning off driver signature verification I truthfully have no idea if that will solve the issue but worth a try I suppose .

    Though for me I might just stay on junes simplix update. Unless a future update somehow fixes this because not trying to be mean here but really don’t want to do yet another clean install lol.
     
  5. johnnypop

    johnnypop MDL Novice

    Feb 11, 2012
    4
    1
    0
    #6 johnnypop, Jul 16, 2023
    Last edited: Jul 16, 2023
    (OP)
    Yeah I'm gona go back to June one in fact I have one made already but when July came out with net.framework update I went straight to July one, on the other hand F8 and disable driver signature enforcement works fine but it shouldnt be needed...
     
  6. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,884
    2,529
    60
    Well, given this little "development", Imma just yoink 23.6.20 and stick to it until msft pulls their head out of their behind(a.k.a probably never).
     
  7. ExiledRose6084

    ExiledRose6084 MDL Junior Member

    Apr 14, 2023
    98
    53
    0
    #8 ExiledRose6084, Jul 16, 2023
    Last edited: Jul 16, 2023
    True & what gets me is they did this because these 3 companies reported these supposed issues "First reported by Sophos, and later Trend Micro and Cisco" No offense but Sophos & trend micro don't really seem all that reputable when it comes to viruses & security.

    Then cisco they make wifi modems, adapters, & etc (unless they don't anymore) but they really arn't a virus/security company.

    Anyway I would buy more into this if these reports where made by more credible virus & malware companies.
     
  8. CaptainSpeleo

    CaptainSpeleo MDL Addicted

    May 24, 2020
    947
    659
    30
    #9 CaptainSpeleo, Jul 20, 2023
    Last edited: Jul 20, 2023
    I did a test clean install of Windows 7 Pro 64-bit with my new install disc which was created last week with the new Simplix update pack (23.7.12) and its add-ons and integrated USB3 drivers.
    Everything went fine, as it has in the past.

    My 4th and 6th generation Intel PC's have a GeForce GTX 645 graphics card, so it requires me running this command as administrator and then rebooting BEFORE installing its driver:
    Bcdedit.exe -set TESTSIGNING ON
    Once that is done, it prevents the code 52 error message from appearing and allows the driver (30.0.14.7444) to install successfully.

    Hopefully, this will address some of the above complaints about code 52 and driver signing in Windows 7.
     
  9. johnnypop

    johnnypop MDL Novice

    Feb 11, 2012
    4
    1
    0
    I thought it was only a few that had an issue with the July pack and driver signature, I see now more people actually have problems with July update and code 52 ""Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. "
     
  10. CaptainSpeleo

    CaptainSpeleo MDL Addicted

    May 24, 2020
    947
    659
    30
    There's nothing wrong with the July 2023 update pack.
    It shouldn't be blamed for the NVIDIA-related driver signing issue.
     
  11. CaptainSpeleo

    CaptainSpeleo MDL Addicted

    May 24, 2020
    947
    659
    30
    Yep, that's the correct process for installing the NVIDIA driver.

    The only downside is the watermark that appears and remains in the lower right corner of the display.

    Capture.JPG
     
  12. bphlpt

    bphlpt MDL Junior Member

    Aug 2, 2010
    60
    36
    0
    Yes, but does that solution work for Win7? the comments at the above link say it only works for Win 8+.
     
  13. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,936
    150
    It's a few KB download with a single button to click.

    Isn't faster to try yourself than asking and waiting for a reply?
     
  14. ExiledRose6084

    ExiledRose6084 MDL Junior Member

    Apr 14, 2023
    98
    53
    0
    I discovered July's update completely corrupts my wifi driver on pretty much everything except for windows 10 home & windows 11 home. Not even turning off driver signature verification fixes it.
     
  15. CZ Eddie

    CZ Eddie MDL Novice

    Mar 20, 2016
    49
    9
    0
    Worked for me.
    Though, I still have BSOD issues.
    I think my BSOD are unrelated to the update pack though, because I'm fairly sure I get them even on test builds prior to the update pack.

    Oh, and my issues are in ESXi VM's. I'm not working with a physical box.

    Random screenshots of my BSODs
    upload_2023-7-25_20-37-14.png
     
  16. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,936
    150

    Why you have nvidia drivers installed if it's a VM?
     
  17. CZ Eddie

    CZ Eddie MDL Novice

    Mar 20, 2016
    49
    9
    0
    I have a video card installed. Can't use it if I don't have the drivers. Passthrough PCIe.