On Thu, Sep 23, 2021 at 10:09 PM Sam Varshavchik wrote:
>
> Go Canes writes:
>
> > On Thu, Sep 23, 2021 at 6:52 PM Sam Varshavchik
> > wrote:
> > > Windows did boot, but came up in 640x480 mode with basic drivers,
> > > unactivated, and refused to activate, wanting me to pay for a license.
> > >
Ed Greshko writes:
In a couple of months, if neither one of my VMs offer a Win11 upgrade I'll
try to switching to an EFI VM, and copy swtpm's data to the new VM's swtpm,
before the first boot, and see what happens…
All I can say is you have more patience with Windows than I have. Way
Go Canes writes:
On Thu, Sep 23, 2021 at 6:52 PM Sam Varshavchik
wrote:
> Windows did boot, but came up in 640x480 mode with basic drivers,
> unactivated, and refused to activate, wanting me to pay for a license.
> The explanation it gave me: new hardware. This was a retail license,
though,
On Thu, Sep 23, 2021 at 6:52 PM Sam Varshavchik wrote:
> Windows did boot, but came up in 640x480 mode with basic drivers,
> unactivated, and refused to activate, wanting me to pay for a license.
> The explanation it gave me: new hardware. This was a retail license, though,
> which should be trans
On 24/09/2021 06:52, Sam Varshavchik wrote:
Sam Varshavchik writes:
Ed Greshko writes:
On 20/09/2021 00:08, Sam Varshavchik wrote:
Is anyone else getting this error in the "Security processor troubleshooting"
(21H1, with all updates installed)?
It has been nearly 2 months since I worked o
Sam Varshavchik writes:
Ed Greshko writes:
On 20/09/2021 00:08, Sam Varshavchik wrote:
Is anyone else getting this error in the "Security processor
troubleshooting" (21H1, with all updates installed)?
It has been nearly 2 months since I worked on this. But, yes, that is what I
was seeing
Ed Greshko writes:
On 20/09/2021 00:08, Sam Varshavchik wrote:
Is anyone else getting this error in the "Security processor
troubleshooting" (21H1, with all updates installed)?
It has been nearly 2 months since I worked on this. But, yes, that is what I
was seeing. No matter what I did
I
On 20/09/2021 00:08, Sam Varshavchik wrote:
Is anyone else getting this error in the "Security processor troubleshooting"
(21H1, with all updates installed)?
It has been nearly 2 months since I worked on this. But, yes, that is what I
was seeing. No matter what I did
I could not get passed t
What finally got my existing Win10 guest VM (originally upgraded from Win7)
to see a TPM2 device was the following process:
1) Make a copy of the raw disk image. This isn't really necessary, but I did
this for backup purposes.
2) In virt-manager I created a new VM, pointing to the existing
