none
WDS issues after installing the 2019-03 cumulative update on Windows Server 2016 RRS feed

  • Question

  • I've set up WDS (with some MDT added for good measure) for our company VMs and computers.

    Yesterday I applied the 2019-03 cumulative update to the WDS server (running Windows Server 2016 Standard) and today, I can't use WDS any more.

    A sample VM will get the initial list of boot images, but regardless of which image I pick, the transfer will stop after a few seconds (with the progress bar having moved a few "squares") and after a minute or so of nothing happening I'll get the generic "A required device isn't connected or can't be accessed" error.

    Checking the WDS logs, the only thing that I found is the following:

    The Following Client failed TFTP Download:

    Client IP: 10.150.4.3
    Filename: \Boot\x64\Images\boot.wim
    ErrorCode: 13
    File Size: 291959795
    Client Port: 9956
    Server Port: 53793
    Variable Window: true

    Again, things were working just fine a few days ago and the only thing that's changed that I can think of is the recent cumulative patch that has been applied.

    Any ideas what might be wrong?

    PS. AFAIK TFTP has error codes from 1 to 9, and I can't find ANY information about error code 13 in relation with TFTP...




    Friday, March 15, 2019 8:51 AM

All replies

  • Hi,

     

    May I confirm if there is any other specific error code on the screen when the issue happened? if so, could you please help to share it, thanks!

     

    In addition, I found a similar post as below, hope it can help.

     

    https://social.technet.microsoft.com/Forums/en-US/cb267f4e-a704-44ad-a444-a8160c30e775/pxe-fails-each-time-with-0xc0000001-quota-required-device-isnt-connected-or-cant-be?forum=configmanagergeneral

     

    Best regards,

    Fei

    ----------------------------------------------------------------------------------------------

    Please remember to mark the replies as answers if they help. Thanks!

    Monday, March 18, 2019 6:27 AM
  • Hi,

     

    May I confirm if there is any other specific error code on the screen when the issue happened? if so, could you please help to share it, thanks!

     

    In addition, I found a similar post as below, hope it can help.

     

    https://social.technet.microsoft.com/Forums/en-US/cb267f4e-a704-44ad-a444-a8160c30e775/pxe-fails-each-time-with-0xc0000001-quota-required-device-isnt-connected-or-cant-be?forum=configmanagergeneral

     

    Best regards,

    Fei

    ----------------------------------------------------------------------------------------------

    Please remember to mark the replies as answers if they help. Thanks!


    I've already posted all the logs I could find. Additionally, the issue is VERY clearly tied to the latest update, not some configuration, as evidenced by more people having the same problem after the latest patches were applied: https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa063ef0-90ef-44c7-b1b7-ce65a2a66119/issues-with-wds-after-march-2019-cumulative-update?forum=winserversetup
    Monday, March 18, 2019 8:12 AM
  • I was having the exact same problem.  The solution for me was on the link you provided (https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa063ef0-90ef-44c7-b1b7-ce65a2a66119/issues-with-wds-after-march-2019-cumulative-update?):

    unchecking Variable Window Size or "Enable Variable Window
    Extension" 
    under the TFTP tab in the WDS Server Properties sheet solved the problem for us

    Monday, March 18, 2019 4:00 PM
  • I was having the exact same problem.  The solution for me was on the link you provided (https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa063ef0-90ef-44c7-b1b7-ce65a2a66119/issues-with-wds-after-march-2019-cumulative-update?):

    unchecking Variable Window Size or "Enable Variable Window
    Extension" 
    under the TFTP tab in the WDS Server Properties sheet solved the problem for us

    I wouldn't call it a "solution". More like a "workaround". ;)

    And, yes, my thread is a duplicate of that other one, basically. Sorry for that. :(

    • Proposed as answer by kurama69 Tuesday, March 19, 2019 3:29 PM
    Monday, March 18, 2019 4:03 PM
  • Thanks man, i was going mad with this!! 

    Gotta love Micro$oft updates ;)

    Tuesday, March 19, 2019 3:20 PM
  • Just wanted to say thanks for the work around above.  I was in the same exact situation.  Applied updates over the weekend and no working WDS on Monday.  Very frustrating!!!!

    areile

    Wednesday, March 20, 2019 3:20 PM
  • Unchecking the "Enable Variable Window Extension" did not work for me on Windows Server 2019, so I ended up removing this update: kb4489899 and all is working fine..  what a silly compromise from Microsoft that we are forced to go with these days.. also kb4489891 has this issue as well.. the issue appears to be a bug in 1809 world.......


    • Edited by OASH Friday, March 22, 2019 1:42 PM
    • Proposed as answer by OASH Wednesday, April 3, 2019 1:55 PM
    Friday, March 22, 2019 1:39 PM
  • I faced the same issue on the Windows 2019 server after 2019-03 update - and I've resolved it with this advice:

    unchecking Variable Window Size or "Enable Variable Window Extension" under the TFTP tab in the WDS Server Properties sheet solved the problem for us

    Friday, March 22, 2019 3:39 PM
  • I faced the same issue on the Windows 2019 server after 2019-03 update - and I've resolved it with this advice:

    unchecking Variable Window Size or "Enable Variable Window Extension" under the TFTP tab in the WDS Server Properties sheet solved the problem for us

    This worked for me. Thanks.

    Skip

    Monday, April 1, 2019 8:41 PM
  • Thank you. Unchecking  the "Enable Variable Window Extension" worked for us.

    -S




    • Edited by Sau Pat Thursday, April 4, 2019 1:48 PM
    Thursday, April 4, 2019 1:47 PM
  • Thanks,  This helped me solve my issues where the client devices were all showing error 0xc0000001 after trying to load the boot image file for 5-10 secs - WDS deployment now working successfully after unchecking "Enable Variable Window Extension"
    Saturday, April 20, 2019 4:47 PM
  • still the same issue with Windows Server 2016 April cumulative update. I had to remove previous cumulative (2019-03) because i don't like half measure decision. And now after installing 2019-04 (Windows10.0-KB4493470-x64) i've got my WDS server down.
    Wednesday, April 24, 2019 9:18 AM
  • Having the same issue, but disabling Enable Variable Window Extension isnt real soultion because some clients wont be able to boot at all without it
    Thursday, April 25, 2019 6:34 AM
  • I had exactly the same problem, the workaround unchecking the "Enable Variable Window Extension" on the TFTP tab did the trick for me on my 2012 R2 WDS server.
    Wednesday, May 8, 2019 11:57 AM
  • Ran into this problem on some production servers, but we noted that it did not effect all (client) hardware platforms and only actual Legacy WDS PXE and not Linux PXE running on the same box. The patch was removed rather than making the "workaround" change, as we were not able to easily determine what that setting would do regarding the other things the server handles and the network configuration. Installation of that update was blocked (and the updates it superceded) and hope that the next CU has this issue fixed.
    Wednesday, May 8, 2019 4:14 PM
  • This also worked for me and I'm using WDS on Server 2012 R2.
    Monday, May 13, 2019 5:08 PM
  • Thx, its work too.
    Friday, May 17, 2019 9:17 AM
  • Thanks, this workaround works for me in 2012 R2, too.
    Friday, May 31, 2019 3:04 AM
  • I was having the exact same problem.  The solution for me was on the link you provided (https://social.technet.microsoft.com/Forums/windowsserver/en-US/aa063ef0-90ef-44c7-b1b7-ce65a2a66119/issues-with-wds-after-march-2019-cumulative-update?):

    unchecking Variable Window Size or "Enable Variable Window
    Extension" 
    under the TFTP tab in the WDS Server Properties sheet solved the problem for us


    Worked liked a charm!
    Tuesday, June 18, 2019 6:54 PM