![]() ![]() I wrote last year about issues with OneNote and OneDrive (now overcome by doing it properly) but goodness knows where the unsynced changes are (again, I found a backup, but it doesn’t have the latest changes in it).Īgain, using the WinRE Command Prompt, I backed up the files I thought were most likely to be missed. The items of most concern to me were some scripts I’d finally got working this afternoon and any notes in OneNote. ![]() If the sync engine can’t authenticate, I’m pretty sure I must be working from a local copy – which will be lost if the PC is rebuilt! All of my data until I changed my password is on servers but anything since then has been failing to sync. With BitLocker disabled, I hoped to be able to restart the PC and boot Windows, but unfortunately it was still not playing ball. I’ll be driving to the office on Monday for someone to take a look at my PC and I suspect a rebuild will be on the cards… Work in progressĭespite the support team’s assurances that all of my data is on servers, I’m pretty sure it’s not. Manage-bde -unlock c: -rp recoverypassword Next, I disarmed BitLocker using the following commands: That’s OK, as long as you have the recovery key and, following the advice in the article linked above, I chose the “Skip this drive” link at the bottom of the page that requests entry of the recovery key, before selecting Advanced options/Troubleshoot/Advanced options/Command Prompt. To terminate this BitLocker recovery loop, I needed to suspend BitLocker from within the Windows Recovery Environment (WinRE). We tried hard resets, turning the TPM on and off in the BIOS and more, until I found a TechNet wiki article that seemed to describe the issue (or at least something very like it). My IT support team gave me my key… and then after a restart we went round the loop again. Each time I entered my BitLocker PIN, I was faced with a message that invited me to use the BitLocker key to recover my PC. Arghhh! /f1gizmxHg0Īfter rebooting, I found that a Windows 10 update hadn’t properly applied. ![]() Restart PC following updates and get this. Stuck in a BitLocker loopįriday the 13th. Unfortunately that “quick reboot to get things working again” turned into a disaster, with an hour long support call, followed by a desperate attempt to recover the last few hours’ work. I try not to reboot my PCs too often – frankly I thought I’d left the days of daily reboots behind with Windows 95 – but, faced with a display driver bug on my Surface Pro 3 (that seems to be triggered by the Azure Portal), a change of password that led to repeated authentication prompts (and OneDrive refusing to sync), together with some software updates pushed to my PC from SCCM, I had little choice this afternoon. Please be warned that the information here may be out of date. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |