This bug was initially created as a copy of Bug #1877721

I am copying this bug because:

This bug is still reproducible on rhel 9.2, with fresh installed windows 10 guest.

Description of problem:
Bitlocker doesn't start to do encryption with fresh installed Win10 guest. But a reboot of the guest, bitlocker can start encryption.

Version-Release number of selected component (if applicable):
RHEL 8.3
Kernel: 4.18.0-234.el8.x86_64
qemu-kvm: qemu-kvm-5.1.0-2.module+el8.3.0+7652+b30e6901.x86_64
edk2: edk2-ovmf-20200602gitca407c7246bf-3.el8.noarch
libptms: libtpms-0.7.2-1.20200527git7325acb477.module+el8.3.0+7068+4e1b8df5.x86_64
swtpm: swtpm-0.3.0-1.20200218git74ae43b.module+el8.3.0+7648+42900458.x86_64

How reproducible:

Steps to Reproduce:
1. Install a win10 guest (q35 + OVMF)
2. Attach vtpm device to win10 guest
3. Inside guest vm run commands:

bdehdcfg -target c: shrink -newdriveletter s: -size 606 -quiet
manage-bde -on c:

reboot system as required.

4. Re-login guest vm after reboot, run command:
manage-bde -status

Actual results:
Encryption is not started
Pop up dialog with Bitlocker could not be enabled. (see attachment)

BitLocker Drive Encryption: Configuration Tool version 10.0.19041
Copyright (C) 2013 Microsoft Corporation. All rights reserved.

manage-bde -status

Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: [Windows]
[OS Volume]

Size: 29.62 GB
BitLocker Version: None
Conversion Status: Fully Decrypted
Percentage Encrypted: 0.0%
Encryption Method: None
Protection Status: Protection Off
Lock Status: Unlocked
Identification Field: None
Key Protectors: None Found

Expected results:

Bitlocker can encrypt win10 guest without issue.

Additional info:

This issue only happens with refresh installed win10 guest. When reboot the guest vm again, and repeat the test steps, bitlocker can start disk encryption.