General discussion


Credant Disk Encryption causes Windows 7 to not boot after SP1 install

By danekan ·
When installing Service Pack 1 onto a Windows 7 system that has Credant disk encryption installed, we're experiencing that all systems indefinitely hang at the reboot on "Starting Windows."My hunch is Windows is trying to read/write/update files that have been previously encrypted w/ Credant and is unable to access, or normally the encryption service would've been started at the point it needs these files and and is failing to start.

A boot into the system recovery DVD and attempt to do a startup repair doesn't fix it, and there seem to be no valid restore points. As far as I know, there should be restore points, and SP1 installer even creates one. So I also think maybe there's an issue there with the restore point being encrypted and unable to be read.

Has anyone using Credant encountered this problem? I can't find much about it on the Internet, and the Credant support forum on their site is locked down and I requested access but they'll only grant it to the named authorized users (which boils down to 3 people probably having access in a very large corporate environment, and those people aren't the ones who are wasting half their day cleaning this up or troubleshooting this)

Is there a 'best practice' with regards to installing SP1 on a non-MSFT-encrypted disk system? Has anyone else encountered this, and have you been able to get the system to boot up by doing anything other than re-imaging and recovering the hard drive by putting it into another system?

Is there any way via recovery console command line to access anything that might be logged? (Sys event log? etc?... I don't think these have even started up by the point it's failing, but I don't really know what point it's at)

I'm seeing a lot of "fatal error" threads related to Service pack 1 that may or may not be applicable ( http://technet.microsoft.com/en-us/library/ff817622%28WS.10%29.aspx for example has some good in depth on how to remove a partially installed SP1) ... I haven't actually tried that procedure yet--tomorrow maybe--but this might not be much more time efficient than re-imaging a new machine w/ SP1 already and recovering data to it)

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Repost as 'Q&A'

by HAL 9000 Moderator In reply to Credant Disk Encryption c ...

Try reposting this in the 'Q&A' forum. The 'Discussion' forum is for matters of general discussion, not specific problems in search of a solution. The 'Water Cooler' is for non-technical discussions. You can submit a question to 'Q&A' here:


There are TR members who specifically seek out problems in need of a solution. Although there is some overlap between the forums, you'll find more of those members in 'Q&A' than in 'Discussions' or 'Water Cooler'.

Be sure to use the voting buttons to provide your feedback. Voting a '+' does not necessarily mean that a given response contained the complete solution to your problem, but that it served to guide you toward it. This is intended to serve as an aid to those who may in the future have a problem similar to yours. If they have a ready source of reference available, perhaps won't need to repeat questions previously asked and answered. If a post did contain the solution to your problem, you can also close the question by marking the helpful post as "The Answer".

Collapse -

thanks will do

by danekan In reply to Repost as 'Q&A'
Collapse -

re: Credant Disk Encryption causes Windows 7 to not boot after SP1 install

by Credant_Tech In reply to Credant Disk Encryption c ...

Hi this is Credant support and we would be happy to help with this. Can you give us a call at 866-CREDANT to discuss?

Collapse -

i've already tried contacting credant support

by danekan In reply to re: Credant Disk Encrypti ...

Your support won't discuss with me because I'm not an "authorized" user on our support contract. Members of the department that purchases Credant presumably are presumably on the authorized list, but they are busy trying to solve other problems. (I think that would make you the only vendor we deal with who doesn't provide access to all to their online public KB.)

Related Discussions

Related Forums