@hkrn Wait, what?
"You can retrieve the BitLocker recovery key by logging into the BitLocker recovery screen portal with your Microsoft account"
So you're telling me, the bitlocker recovery key is uploaded to Microsoft without consent or knowledge?! (I don't use Windows, so I cannot check this.)
That'd be a huge risk - both for companies and individuals: compromised cryptographic keys.
#Windows 10 KB5058379 update triggers #BitLocker recovery on some devices
BitLocker Encryption Bypassed in Minutes Using Bitpixie Vulnerability
A critical vulnerability in Microsoft’s BitLocker full disk encryption, demonstrating that it can be bypassed in under five minutes using a software-only attack dubbed “Bitpixie”
https://cybersecuritynews.com/bitlocker-encryption-bypassed/
NEW on We 
Open Source
HP Pavilion locked by BitLocker? @linuxnerd tackled it with open source tools, wiped the encrypted NVME with dd, and installed Fedora 41 KDE.
Read the full breakdown of this Linux rescue: https://allthingsopen.org/articles/how-to-install-linux-remove-bitlocker-encryption
Talking with the folks in the local #vintage / #retrocomputing community, they clued me in that the #ThinkPad #RAID is a steaming pile of 
and not worth the trouble.
Oh well. Thanks for cluing me in
So I swapped out the two testing #NVMe drives I was using and reinstalled the original sticks - to have #windoz10 demanding for the #bitlocker recovery key. 
Well, time to wipe & install #windoz11 then.
Install went fine, only 4 rando #drivers to find for all #devices to be recognized and working.
Using my #CTT scripts to install the majority of applications, then to remove the #spyware #bloatware and other garbage #micro$oft added to #windows11
Then migrate my #data from my other ThinkPad. Welcome to my #sunday #funday
#siliconValley #SillyValley #sanfrancisco #sanfran #sanfranciscocomputers #sanfrancomputers #sanfranciscovintagecomputers #sanfranvintagecomputers #sanfranciscovintagehardware #sanfranvin-tagehardware
#vintagecomputing #vintagecomputint #vintagecomputer #vintagecomputers #vintagecomputalk
#vintagehardware #computerHistory #retro #VCF #vintageComputerFestival
#retrocomputing #retroComputers #WallOfRetro #retroTech #retroTechnology
#nerdsOfVintage #happyNerding
#computer #tech #computerHardware #laptop #laptops
#IBM #thinkpad #thinkpads #VintageThinkPad #X86 #WindowsVista #IBMhardware #lenovoHard-ware #Thinkpadnium
#upcycle #restore #TechnologyRepair #ThinkPadRepair #WasteNotWantNot #Thinkpadnium
#makeShitMonday #showmewhatyougot
As a follow-up to Full Disk Encryption for those moving from #Windows10, #openSUSE offers #FDE secured by TPM2 or FIDO2 for #BitLocker-like security. 
#10isEnough #EndofWindows10 #UpgradetoFreedom today! https://news.opensuse.org/2024/09/20/quickstart-fde-yast2/
I’ve updated my bitlocker attacks list https://github.com/Wack0/bitlocker-attacks
The main addition here is documentation of “break out in hives” (CVE-2024-20666, nice) and its variant (CVE-2025-21213).
The most interesting thing here is that it’s technically still not fixed - the fix was only applied to the PCA2023-signed bootmgr_ex, so without the KB5025885 mitigations applied (and other default settings which nobody ever changes), you’re still vulnerable without even needing a downgrade attack for bootmgr.
(If you’re using TPM-only bitlocker, you really should be using legacy integrity validation - that is, Allow Secure Boot for integrity validation policy DISABLED with PCRs 0,2,4,7,11 set - legacy integrity validation was never vulnerable to these issues in the first place! This would imply bitlocker potentially going into recovery more often with windows updates, but it’s a choice between that and currently broken bitlocker vulnerable to various boot-time software issues combined with downgrade attacks)
The main issue here is that starting from Windows 10 (th1), the systemdatadevice element was added to winload; if present the SYSTEM hive is loaded from this block device instead of the (bitlocker encrypted) OS partition.
Therefore, the first (easiest) exploitation method was to pull a SYSTEM hive from boot.wim, modify it to set SYSTEM\Setup!CmdLine to cmd.exe, and set up the WinRE boot entry to use it; booting WinRE would then pop a SYSTEM shell with bitlocker keys derived and in memory.
The original fix just removed the systemdatadevice support from winload, but (at least in some cases) the older revisions of winload (for the same major Windows version) would still boot Windows successfully; thus the second exploitation method: configure BCD to load winload from somewhere else (downgrade attack), booting the bitlocker-encrypted OS with custom SYSTEM hive taken from install.wim - it turned out that without winpe also set, this corrupted the SYSTEM hive on the bitlocker-encrypted OS partition; also the Win32 subsystem would fail to load, but native code execution would still work when setting SYSTEM\ControlSet001\Control\Session Manager!SetupExecute. Therefore, I took the old Native Shell codebase, ported it to AMD64, and modified it to acquire SeRestorePrivilege and open files with FILE_OPEN_FOR_BACKUP_INTENT (so permission checks would be ignored, so it’s possible to do the sethc trick at this point).
This Week in Security: IOCONTROL, (Location) Leaking Cars, and Passkeys - Claroty’s TEAM82 has a report on a new malware strain, what they’re calling IOCONT... - https://hackaday.com/2025/01/03/this-week-in-security-iocontrol-location-leaking-cars-and-passkeys/ #thisweekinsecurity #hackadaycolumns #doubleclickjack #securityhacks #bitlocker #news
@puppygirlhornypost2 @navi yeah, but that's a common problem based off #TechIlliteracy and lack of proper explaination!
Bonus points if #TPM bs prevents #DataRecovery.
Reason #9001 why #Windows is #unfixable, broken #Govware and #Microsoft is blatantly evil:
Instead of actually fixing their shitty #BitLocker #encryption [which has #Govware #Backdoors BTW!] they pushed a broken update and instead of fixing that they told users nonchalantly to 'go fuck yourself' and instead expected them to run some shitty #PowerShell, which then allowed #CyberCriminals to prey upon #TechIlliterates by shoving malicious stuff at them...
Case in point: This is just inexcuseable espechally for a #CCSS that costs hundreds of dollars retail [ #OEM-Keys don't count! ]...
Bitlocker will even be available on Windows 11 Home!
Microsoft is enabling BitLocker device encryption by default on Windows 11
https://www.theverge.com/2024/8/14/24220138/microsoft-bitlocker-device-encryption-windows-11-default
Any #bitlocker bypass out there for Windows Server 2008 R2? #WS2K8R2
Asking for a friend
"It felt like a bad idea to read a 48-character key to people who were already stressed out," Woltz told The Register.
https://www.theregister.com/2024/07/25/crowdstrike_remediation_with_barcode_scanner/
Microsoft can't seem to catch a break!
July Windows update is sending PCs into recovery
https://www.pcworld.com/article/2407581/july-windows-update-sending-pcs-into-bitlocker-recovery.html
Tune in tomorrow (Sunday) at 11AM ET/8AM PT for the latest episode of #IanAndJaySpaceOut and you can spend an hour watching @jay and I try to guess the #BitLocker key for our #Windows laptop.
I think today is the day that I install the new CPU/RAM in my gaming PC. I've been sitting on a new 5900X and 64GB of DDR4 for a couple months because I'm always nervous about spreading new thermal paste. The specter of losing the 72TB of pirated videogames due to some weird bitlocker problem always looms.
Raspberry Pi Bitlocker hack is a new spin on a years-old, well-documented exploit - Enlarge / A $10 Raspberry Pi Pico-based TPM sniffing tool, designed to ... - https://arstechnica.com/?p=2002304 #bitlocker #microsoft #windows #tech #tpm
This just in...
Bad news for #BitLocker users — its encryption can be cracked remarkable easily it seems.
