Windows Update Failures in Japanese-Localized Azure VM SQL2022-WS2022 Images: Cause and Workaround

This blog post is designed specifically for our customers in the Japan region, and as such, it is also written in Japanese. If you prefer to read it in English, please click the link Jump to English below to access the English section.

Hello from the SQL Server Support Team.

In this article, we’ll address a common issue that arises when you deploy an Azure Marketplace image containing SQL Server (like SQL2022-WS2022) and localise the operating system to Japanese. After May 2026, you might find that Windows Updates do not install correctly, failing with error codes like 0x800f081f or 0x800f0831.

Windows updates might fail to install, leading to error messages that look something like this:

Error: “There was a problem during the installation of the updates, but it will automatically retry later. If this issue persists and you need to gather more information via web search or support inquiries, the following error code may be helpful: (0x800f081f).”

Note: The error code may also show as 0x800f0831 in some instances.

This problem can stem from issues within certain Marketplace images that include SQL Server. Fortunately, this issue has been fixed in the latest images, so it won’t affect any new servers deployed from these updated images.

If you see a warning in C:\Windows\Logs\CBS\CBS.log that indicates the following manifest file is missing, it likely means your system is affected:

amd64_microsoft-hyper-v-ram-parser.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_531076835e0e2f98.manifest

Log file: C:\Windows\Logs\CBS\CBS.log

2026-05-19 12:11:57, Info CBS Exec: Warning – Manifest doesn’t exist for: \\?\C:\Windows\CbsTemp\31254331_3251161130\Windows10.0-KB5087545-x64.cab\amd64_microsoft-hyper-v-ram-parser.resources_31bf3856ad364e35_10.0.20348.1_ja-jp_531076835e0e2f98.manifest 

Important Points to Remember:

• Ensure you have an Azure Backup of the Azure VM before making any changes so that you can restore it to its previous state if needed.
• Stop the SQL Server service before starting the maintenance tasks, and set its startup type to Disabled.
• After you complete the tasks, reset the SQL Server service startup type to its original status (e.g., Automatic or Automatic (Delayed Start)).
• Do not restart the OS immediately after re-adding the Japanese language pack until you have reapplied the updates. Restarting prematurely could lead to issues, such as not being able to connect via Remote Desktop due to version mismatches between the OS binaries and the language resources.

Steps to Uninstall the Japanese Language Pack:

1-1. Open Command Prompt as Administrator.

1-2. Run the command below to uninstall the Japanese language pack:

lpksetup /u ja-JP

1-3. Restart your computer.

1-4. Log in using an account that previously displayed the Japanese interface and ensure that it now appears in English.

Note:

• If Japanese is still listed as the preferred language, you can remove it from the settings by moving it down the list and clicking Remove.

Next, we need to reinstall the Japanese language pack and then reapply the Windows updates. The steps will vary based on your server’s ability to connect to Windows Update endpoints.

Step 2: Download the Corresponding MSU File

Grab the .msu file that matches the version of the update currently installed on your server from the Microsoft Update Catalog.

Visit the Microsoft Update Catalog here: https://www.catalog.update.microsoft.com/home.aspx

To Identify Your Installed Update Version:

1. Run “winver”.
2. Note the OS build number from the dialog that appears.
3. Use this build number to identify the relevant update from the Windows Server 2022 update history page.

You can find the Windows Server 2022 update history here: Windows Server 2022 Update History

Step 2-2: Reinstall the Japanese Language Pack (when online)

Follow these steps:

2-2-1. Go to Settings > Time & Language > Language & Region and click Add a language.

2-2-2. From the options, select 日本語 (Japanese) and click Next.

2-2-3. On the Install language features screen, make sure to choose Language pack and then click Install.

2-2-4. Wait until the installation finishes.

2-2-5. After installation, log out and log back in. You should now be able to select Japanese as your preferred display language.

2-3. Open Command Prompt as Administrator once again.

2-4. Extract the Downloaded MSU File:

2-4-1. Create directories for your work:

md

md

2-4-2. First extraction:

expand -f:Windows*.cab

2-4-3. Second extraction:

expand -f:*

2-5. Now, reapply the update using the extracted files:

DISM /Online /Add-Package /PackagePath:\

2-6. After reinstalling the language pack, attempt to install the latest updates again and check that the issue is resolved.

In summary, this guide provides an overview of troubleshooting and safeguarding your SQL Server in the Azure environment, specifically in keeping up to date with necessary language packs and updates. Following these instructions will help ensure everything runs smoothly.

FAQs

• What should I do if I cannot connect to the server via Remote Desktop after reinstallation of the language pack?

  Make sure to follow the restart and update steps carefully. If problems persist, ensure the versions of the OS and language files are compatible.

• How can I check which updates are installed on my server?

  Run the “winver” command in the Run dialog to find your OS build, then refer to the Windows Update History for details on installed updates.

• Where can I find more information if I encounter additional error messages?

  The Microsoft support pages often provide relevant troubleshooting steps. You may also check forums for other user experiences with similar issues.

Thanks for reading!