In the process we unfortunately exposed a bug. In Windows Server 2019 we made several changes to the virtual machine firmware (a topic that I plan to blog about another day). We have been digging into these issues and have identified the root cause. If the problem persists, contact Product Support. ![]() ‘Test VM 1’ was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support for the guest operating system. ‘Test VM 1’ has encountered a fatal error but a memory dump could not be generated. People are seeing error messages like the following:Ĭritical 16:13:49 Hyper-V-Worker 18604 None In the last couple of weeks, we have been hearing reports from customers who are encountering problems after migrating virtual machines directly from Windows Server 2012 R2 to Windows Server 2019. ![]() UPDATE: This issue is now resolved in the cumulative update (KB4497934)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |