Cara Mengatasi Bitlocker Recovery Windows 11

0 views
Skip to first unread message
Message has been deleted

Floriana Monterroza

unread,
Jul 14, 2024, 11:34:50 PM7/14/24
to kluscortuovo

Jika Anda mengalami komputer menampilkan layar recovery BitLocker setelah dinyalakan, berarti HDD/SDD telah dienkripsi. (HDD/SDD terkunci.) Setelah komponen hardware PC diganti atau pengaturan BIOS diubah, semua dapat menyebabkan sistem menampilkan layar pemulihan BitLocker setelah dihidupkan. Oleh karena itu, Anda perlu memberikan kunci pemulihan untuk mengatasi masalah ini, silakan lihat langkah pemecahan masalah berikut. Jika Anda tidak bisa memasukkan kunci pemulihan untuk membukanya, cara lain adalah dengan melakukan proses instalasi ulang Sistem Operasi.

Catatan: BitLocker adalah produk keamanan enkripsi Microsoft, Asus tidak menyimpan atau memiliki kemampuan untuk menyediakan kunci pemulihan. Asus tidak dapat menghindari proses kunci Microsoft BitLocker Recovery.

cara mengatasi bitlocker recovery windows 11


Descargar archivo >>> https://bltlly.com/2yP52e



Catatan: Jika HDD/SSD Anda menggunakan enkripsi Perangkat atau enkripsi BitLocker Standar, Anda mungkin melihat gambar berikut saat HDD/SSD dilindungi. Di sini Anda dapat mempelajari lebih lanjut Enkripsi perangkat & Enkripsi Standard BitLocker .

Jika Anda menyimpan recovery key ke akun Microsoft Anda, sign in ke Microsoft account Anda di perangkat lain untuk menemukan recovery key Anda. Jika Anda adalah akun organisasi dengan menggunakan email kantor atau sekolah, Anda dapat mencoba masuk dengan ( ) untuk menemukan recovery key Anda.

BitLocker memastikan bahwa recovery key telah dibackup dengan aman sebelum mengaktifkan perlindungan. Ada beberapa tempat recovery key Anda, tergantung pada pilihan yang dibuat saat mengaktifkan BitLocker:

The manner in which this particular update has been handled has been poor in my opinion. The update is only being pushed out to Windows update or Windows update for business and is not on the Microsoft catalog nor WSUS. So this update has been pushed to machines that I would call "lightly" managed or "unmanaged". Some of these impacted machines have no TPM chip nor do they have bitlocker installed so the need for this update is nil.

The communication thus far has been to instruct us to manually attempt to resize partitions which are not easy to do for anyone, and particularly not for a lot of machines. There are few tools that I can see that let us know if we're going to hit this issue other than to attempt to install and see if it fails. The PowerShell script is not something I'd have my 95 Dad want to do to his machine, let alone me wanting to do it to a bunch of machines at the office.

We're now at Friday, right before patching weekend and may I request a lot more communication and perhaps someone going back and adding in detection into the patch to at least not attempt to install on machines that have no tpm chip and do not have bitlocker installed. These machines are not at risk.

@Arto_Montonen I deleted partition 3 which was WinRE. I created a new NTFS partition without name and drive letter via Windows Disk Management. In the CMD window, I changed the partition ID number. I using the disk part program, when the correct disk and partition have been selected. The ID number can be viewed with the det part command and the set part 27 command sets the ID number, which is the recovery ID partition number of the MBR disk. After that, WinRE starts pointing to disk 0 and partition 3 again when I enable WinRE function again.

I managed to repair the partitions manually with the diskpart program and Microsoft's MBR disk instruction is incorrect and leads to errors, but the GPT disk instruction works. Microsoft made a mistake when it combined the instructions for MBR and GPT disks into one instruction, it led to errors in the MBR disk instruction. Formatting works differently on MBR and GPT disks.

I updated one version of Windows 10 Home PC last week and it didn't get stuck with this error. The user had forgotten the windows PIN code and claimed it was 0000, but that is no longer allowed by Microsoft. I found the e-mail address and password of his Microsoft account, which I used to change the new PIN code. His computer hadn't been used for over 6 to 12 months because logging into Windows 10 Home didn't work. The Windows PIN code can be changed if Microsoft account email address and password have been written down on a piece of paper.

I've found the easiest and safest workaround for Windows RE update problem is to (1) disable Windows RE, (2) change the Windows RE partition type from "Recovery" to "Primary", (3) enable Windows RE, apply the update, then repeat the first three steps, changing the partition type back to "Recovery". You don't need to resize or delete partitions.

WARNING: The steps below involve making changes to your hard disk's partition table. Any misstep could render your system unbootable and potentially result in data loss. This may not work for everyone. Stop if your results at any step are inconsistent with those shown below. Proceed at your own risk.

@shanen0 I'm sure the "you" you're referring to is Microsoft and not Susan Bradley. Susan is a long-time member of the IT community whose invaluable contributions have benefitted IT professionals everywhere. Susan isn't a Microsoft employee, yet she donates countless hours helping others to navigate the complexities of managing Microsoft products and services in an enterprise and small business environment. A true MVP.

Jika Anda mengalami komputer menampilkan layar recovery BitLocker setelah dinyalakan, berarti HDD/SDD telah dienkripsi. (HDD/SDD terkunci.) Setelah komponen hardware PC diganti atau pengaturan BIOS diubah, semua dapat menyebabkan sistem menampilkan layar pemulihan BitLocker setelah dihidupkan.

Oleh karena itu, Anda perlu memberikan kunci pemulihan untuk mengatasi masalah ini, silakan lihat langkah pemecahan masalah berikut. Jika Anda tidak bisa memasukkan kunci pemulihan untuk membukanya, cara lain adalah dengan melakukan proses instalasi ulang Sistem Operasi.

d3342ee215
Reply all
Reply to author
Forward
0 new messages