Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Siegfried Beitl

My feedback

  1. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Virtual Machines » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature

    An error occurred while saving the comment
    Siegfried Beitl commented  · 

    This issue is still unresolved in 2021. This time it is Windows Server 2019. The server reboots to install update KB4601345 and never comes back online again.

    The VM is of the size B1ms (2 GB RAM) running Windows Server 2019 with desktop experience. The minimum requirement for desktop experience is 2 GB . It should work.

    Chain of events as per system event log:
    source WindowsUpdateClient, event ID 20
    Installation Failure: Windows failed to install the following update with error 0x80073712: 2021-02 Cumulative Update for Windows Server 2019 for x64-based Systems (KB4601345).

    source Resource-Exhaustion-Detector, event ID 2004
    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: TiWorker.exe (1792) consumed 448884736 bytes, MsMpEng.exe (2644) consumed 192962560 bytes, and dns.exe (2688) consumed 134303744 bytes.

    source Kernel-Tm, event ID 1
    The Transaction (UOW={5c4300e8-7b5d-11eb-af60-000d3a7ad8c2}, Description='') was unable to be committed, and instead rolled back; this was due to an error message returned by CLFS while attempting to write a Prepare or Commit record for the Transaction. The CLFS error returned was: 0xC0190052.

    Siegfried Beitl supported this idea  · 

Feedback and Knowledge Base