LPD Service stops after CVE-2024-38027

Anonymous
2024-07-11T09:18:26+00:00

I've already 3 different servers (Win2016-Win2022-Win11) that have LPD Service stopping/crashing after applying July Updates with CVE-2024-38027 

Anybody else with same problem? Removing Updates solved the problem but it's not the ideal solution.

Windows for business | Windows Server | Devices and deployment | System management components

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-08-16T09:16:39+00:00

From Microsoft Information it is solved now with August Patchday.

Windows Server 2022:

Printing jobs using LPD protocol might fail with the July 2024 security update <br>Issue was reported by organizations after installing the Windows July security update OS Build 20348.2582 <br>KB5040437 <br>2024-07-09 Resolved <br>KB5041160 2024-08-13 <br>10:00 PT

Windows Server 2019:

Printing jobs using LPD protocol might fail with the July 2024 security update <br>Issue was reported by organizations after installing the Windows July security update OS Build 17763.6054 <br>KB5040430 <br>2024-07-09 Resolved <br>KB5041578 2024-08-13 <br>10:00 PT

Windows Server 2016:

Printing jobs using LPD protocol might fail with the July 2024 security update <br>Issue was reported by organizations after installing the Windows July security update OS Build 14393.7159 <br>KB5040434 <br>2024-07-09 Resolved <br>KB5041773 2024-08-13 <br>10:06 PT

Was this answer helpful?

4 people found this answer helpful.
0 comments

91 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-22T12:18:01+00:00

    I got an update from MS Support. It is finally recognized as a issue. This is what i got from them

    The issue you are currently facing is a known Issue from our end. Our engineering team is working on same actively but meanwhile one of the way to mitigate the issue is rollback of the KB or KIR(.msi for rollback).  Below are the links for KIR:

    1 Windows Server 2016 <br>Windows 10 1607 <br>(RS1) https://download.microsoft.com/download/fe995620-5b0f-40e7-9edb-0fc48e18caf3/Windows 10 1607 and Windows Server 2016 KB5040434 240715_20501 Known Issue Rollback.msi
    2 Windows Server 2019<br><br>Windows 10 1809<br><br>(RS5) https://download.microsoft.com/download/7ea86987-63da-42b3-8b4a-47ddf4c3fbd3/Windows 10 1809 and Windows Server 2019 KB5040430 240715_21101 Known Issue Rollback.msi
    3 Windows Server 2022 (Fe) https://download.microsoft.com/download/2d33031a-c726-4cae-8060-27d65be8134c/Windows Server 2022 KB5040437 240715_20301 Known Issue Rollback.msi

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments
  2. Anonymous
    2024-07-12T07:15:04+00:00

    We have the same issue since July update with our test servers .

    So we stopped the updates for our productive servers till there is a fix from Microsoft .

    Faulting application name: svchost.exe_LPDSVC, version: 10.0.17763.3346, time stamp: 0xb6a0daab
    Faulting module name: ntdll.dll, version: 10.0.17763.5933, time stamp: 0x28f68183
    Exception code: 0xc0000374
    Fault offset: 0x00000000000fb199
    Faulting process id: 0x8dc
    Faulting application start time: 0x01dad340b508fe35
    Faulting application path: C:\Windows\System32\svchost.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-07-11T16:22:56+00:00

    I found info that says it's KB5040430

    So uninstalling this KB should sort but how do you avoid this update in the future or get the other updates in this KB5040430 butt not the one that causes the issue for LPD (CVE-2024-38027).

    Or will Microsoft fix this ?

    thx

    R

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-07-26T21:52:59+00:00

    Note that the KIR installs a GPO and you have to run gpedit.msc and set the new GPO created under Computer Configuration -> Administrative Templates -> KB504043{X} 240715_20501 Known Issue Rollback -> Windows Server {XXXX} - set i to Disabled and reboot for it to work. Thsi happened on 9 of my servers after applying KB5040434

    ...that is the temporary fix until the permanent fix is released in August.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments