Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Taking a quiesce snapshot of Windows Server 2019 virtual machine fails (60395)

Last Updated: 2/19/2020Categories: TroubleshootingTotal Views: 68333Language:
Chinese (Simplified)JapaneseEnglish

41 like this article

Subscribe to get an email
newsletter with new updates

41 people found this helpful Please provide article feedback:

Symptoms

Taking a quiesce snapshot of Windows Server 2019 virtual machine fails.

You get an error similar to:

An error occurred while taking a snapshot: Failed to quiesce the virtual machine.

In the vmtools vss logging, you see entries similar to:

2019-07-02T11:32:11.050Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotRequestor::NeedWaitForSnapshotCompleted():1082: enter
2019-07-02T11:32:11.190Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotProvider::OnLunEmpty():716: 0x000002BB00A65C30
2019-07-02T11:32:11.190Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotProvider::OnLunEmpty():716: 0x000002BB00A65C30
2019-07-02T11:32:11.205Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotProvider::AbortSnapshots():677: 0x000002BB00A65C30
2019-07-02T11:32:11.216Z| vmx| I125: Guest: [  info] [vmvss:vmvss] CVmSnapshotRequestor::WaitForOperation():3364: Unexpected esult from QueryStatus(): 0x800423f9
2019-07-02T11:32:11.217Z| vmx| I125: Guest: [ warning] [vmvss:vmvss] CVmSnapshotRequestor::WaitForOperation():3373: Async opeation result: IDispatch error #8697
2019-07-02T11:32:11.218Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotRequestor::DoSnapshotSet():1904: failed call: et = WaitForOperation(async), result = 0x800423f9
2019-07-02T11:32:11.218Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotRequestor::Finalize():2616: enter
2019-07-02T11:32:11.242Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] CVmSnapshotRequestor::UnmountSnapshotVolumes():2439: enter
2019-07-02T11:32:11.242Z| vmx| I125: Guest: [  debug] [vmvss:vmvss] VDSHelper::ForEachVolume():206: enter

There is error log in the Application Log of Windows Events.

An expected hidden volume arrival did not complete because this LUN was not detected.

Cause

This issue occurs when Windows is unable to identify the recovery volume that is included in the VSS SnapshotSet during the VSS process.

The issue only happens when the Windows 2019 VM is EFI-boot, has the recovery volume and the system disk is GPT disk. It is identified as Microsoft VSS bug.

Resolution

This issue is resolved in Windows Server version 1809 and all versions of Windows Server 2019 OS Build 17763.1012. For more information, see January 23, 2020—KB4534321 (OS Build 17763.1012).

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Workaround

There are 2 options to work around this issue:

Option 1 - Use BIOS boot and MBR disks since Windows 2019 installation

For EFI systems, Microsoft requires Windows should be installed on GPT disks. So it’s suggested to resolve this issue by using an MBR disk layout instead of GPT while provisioning the machines.

Note: MBR can be used if the disk is <= 2TB. If a machine already has GPT, backup all the data from the disk, and convert the disk to MBR . For more information, see the Microsoft article Convert a GPT disk into an MBR disk.

Option 2 - Fall back to the filesystem-consistent snapshot

Navigate to %SystemDrive%\ProgramData\VMware\VMware tools.

Create/edit the Tools.conf file with a text editor.

Add this entry (Or modify existing entry as required).
[vmbackup]
vss.disableAppQuiescing = true

Save the file.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant