- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Who Me Too'd this topic
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2023 09:15 AM - last edited on 02-22-2023 03:04 AM by support_s
02-20-2023 09:15 AM - last edited on 02-22-2023 03:04 AM by support_s
Win 2022 February patches can make windows not boot - No solution from VMWare - KB90947
There is an issue with this months MS patches where after a Windows server 2022 VM running on ESX Below v8 with Secure Boot enabled is patched, it will not boot up. Not sure what were supposed to do here, VMWare's stance seems to be to upgrade to VSphere 8... See links below. Need some advise from the HPE folks on this.
My workaround for the short term was to disable secure bot on the VM's affected.
See "Issues known in this update section":
See VMWare response:
https://kb.vmware.com/s/article/90947