diff --git a/0010-docs-virt-v2v.pod-Document-Windows-vTPM-and-BitLocke.patch b/0010-docs-virt-v2v.pod-Document-Windows-vTPM-and-BitLocke.patch
new file mode 100644
index 0000000..1fdbdee
--- /dev/null
+++ b/0010-docs-virt-v2v.pod-Document-Windows-vTPM-and-BitLocke.patch
@@ -0,0 +1,47 @@
+From 2d1fbff24a71cab66a3c27e4db383c076eb5f71c Mon Sep 17 00:00:00 2001
+From: "Richard W.M. Jones" <rjones@redhat.com>
+Date: Tue, 13 Jan 2026 12:33:11 +0000
+Subject: [PATCH] docs/virt-v2v.pod: Document Windows vTPM and BitLocker
+ Recovery
+
+Reported-by: Ming Xie
+Fixes: https://issues.redhat.com/browse/RHEL-103915
+(cherry picked from commit 859c43b1eb81cfdcb5f481b571e2c387860f8a27)
+---
+ docs/virt-v2v.pod | 23 +++++++++++++++++++++++
+ 1 file changed, 23 insertions(+)
+
+diff --git a/docs/virt-v2v.pod b/docs/virt-v2v.pod
+index 871ca521..9fbc2694 100644
+--- a/docs/virt-v2v.pod
++++ b/docs/virt-v2v.pod
+@@ -1587,6 +1587,29 @@ L<https://issues.redhat.com/browse/RHEL-70840>
+ and
+ L<https://windowstechpro.com/how-to-enable-bitlocker-on-windows-11/>
+ 
++=head2 Windows: "Enter the recovery key for this drive"
++
++After conversion, you may be presented with a Windows boot screen showing:
++
++ BitLocker recovery
++ Enter the recovery key for this drive
++ [|___________________]
++
++(See screenshot on L<https://issues.redhat.com/browse/RHEL-103915>)
++
++This happens when the Windows BitLocker disk encryption key is
++contained in the VMware Virtual Trusted Platform Module (vTPM).  The
++vTPM is working I<exactly as designed>.  It is preventing the
++encrypted disk from being moved from one machine to another by storing
++the encryption key in trusted storage on the source.  By design, we
++cannot access or move this key to the target.
++
++To start the VM you will need to enter the BitLocker recovery key.
++This will also register the disk against the new vTPM on the target,
++so it should only be necessary to do this once.
++
++For help finding the recovery key: L<https://aka.ms/recoverykeyfaq>
++
+ =head2 Networks and bridges
+ 
+ Guests are usually connected to one or more networks, and when
diff --git a/virt-v2v.spec b/virt-v2v.spec
index 6782dad..52fd4dc 100644
--- a/virt-v2v.spec
+++ b/virt-v2v.spec
@@ -74,6 +74,7 @@ Patch0006:     0006-RHEL-point-to-KB-for-supported-v2v-hypervisors-guest.patch
 Patch0007:     0007-RHEL-tests-Remove-btrfs-test.patch
 Patch0008:     0008-RHEL-Add-warning-about-virt-v2v-in-place-not-being-s.patch
 Patch0009:     0009-RHEL-output-output.ml-Remove-cache-none.patch
+Patch0010:     0010-docs-virt-v2v.pod-Document-Windows-vTPM-and-BitLocke.patch
 
 BuildRequires: autoconf, automake, libtool
 BuildRequires: make
@@ -408,6 +409,8 @@ done
   resolves: RHEL-135617
 - Hard depend on libnbd 1.24
   resolves: RHEL-140894
+- Add documentation about BitLocker Recovery
+  resolves: RHEL-103915
 
 * Thu Aug 21 2025 Richard W.M. Jones <rjones@redhat.com> - 1:2.8.1-9
 - Rebase to virt-v2v 2.8.1