From: ToddAndMargo <ToddAndMargo@zoho.com>
To: virt-tools-list@redhat.com, kvm@vger.kernel.org
Subject: Windows-11 22H2 upgrade problems
Date: Wed, 5 Oct 2022 23:34:53 -0700 [thread overview]
Message-ID: <6e10d10b-8e64-0d4b-7bbf-f0478743b664@zoho.com> (raw)
Hi All,
Fedora 36
qemu-kvm-6.2.0-15.fc36.x86_64
Windows 11 Pro
Any of you guys having troubles upgrading Windows-11
build 21H2 to 22H2?
I am upgrading from the ISO:
https://www.microsoft.com/en-us/software-download
/windows11
using the US English version:
Win11_22H2_English_x64.iso
The install goes all the way through the process and
when It does its final reboot, it throws the "Installation
failed in SAFE_OS phase with an error during BOOT
operation 0xC1900101 0x20017".
According to
https://www.yourwindowsguide.com/2021/08/troubleshoot-windows-11-upgrade-failures.html
the log file for SafeOS errors is:
C:\$Windows.~BT\Sources\Panther: File named
Setupact.log records actions in the downlevel
and SafeOS phase. As the log can be very
large, setup also creates a file named
“Setuperr.log” that only has information
about the errors encountered by the Setup
to narrow the source of the problem.
And from the same reference:
Error Code Troubleshooting
C1900101-20017 A driver has caused an illegal
operation. Make sure all unnecessary devices
are disconnected except the keyboard and mouse.
Remove any 3rd party anti-virus.Make sure BIOS
firmware is updated on the motherboard.
which means there is a problem with a driver. I removed everything
except the keyboard and mouse. No joy.
And I can't find anything in the logs either.
It also begs the issue of why 21H2 is "safe" and 22H2
is not.
Any of you experiencing this? If so, how did you
work around it?
Many thanks,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~
Yesterday it worked.
Today it is not working.
Windows is like that.
~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2022-10-06 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 6:34 ToddAndMargo [this message]
2022-10-06 16:05 ` Windows-11 22H2 upgrade problems Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e10d10b-8e64-0d4b-7bbf-f0478743b664@zoho.com \
--to=toddandmargo@zoho.com \
--cc=kvm@vger.kernel.org \
--cc=virt-tools-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).