Hi Blender, Regardless of whether renaming the file does the job or whether the presence of the encrypted file prompts windows to see it as a corrupted file and automatically replace it, the method I detailed has allowed me to get several machines to boot to a desktop today. I'm sure that you guys may come up with a more elegant way of reviving those machines presently going around in circles rebooting into a bluescreen but for now, in the absence of any other solution, it's a starting point. Folks could instead use command prompt from the advanced recovery console and copy the file found at x:\windows\system32\ntdll.dll into place at c:\windows\system32 instead or even type SFC /scannow at the command prompt to force windows to fix the issue.