My symptoms are different than the ones in this thread and I don't want to hijack it so I'm starting a new one. Mods please combine the threads if appropriate.
I've opened a support ticketed but I hope a forum discussion might lead to some insight. Considering the other forums posts I've found I'm not hopeful that Bitdefender will have a solution but they may surprise me. I'll leave out my normally snarky comments 
except for this one: The first thing support asked is that I uninstall Malwarebytes which I did and it did not resolve the issue. If you've seen my other posts I'm not on board with with Bitdefender's "Malwarebytes bad!" philosophy but that's way off topic here.
Rescue Mode doesn't work on either of my Windows PCs so I assume it's a local configuration issue. Both PC's config is Windows 7 x64 Ultimate, UEFI install (not legacy BIOS), GPT partitioned SSD drive. I'm ignoring that one is a laptop and the other a desktop, and the drives are SSD. I assume it is UEFI or GPT (and why GPT would make a difference I don't know but at this point it's just information). I confirmed Rescue Mode works in a virtualized Windows 7 x64 environment to eliminate Windows 7 x64 as being part of the problem.
The laptop kept reporting there wasn't enough space on the drive which I know isn't correct. I deleted all the Rescue Mode files from the root of C: and did a repair of BDTS and the error message changed to notify me Secure Boot was enabled. I went into the laptop Setup and changed from UEFI only to allow both UEFI and legacy BIOS (turned off Secure Boot) and to boot legacy BIOS first. After that the previous "not enough space on disk" message came back. I also tried BIOS only.
I swapped in the original HDD that came with the laptop which is an MBR formatted drive and a BIOS Windows installation. Sure enough, Rescue Mode worked like a champ. With Malwarebytes running (oops, sorry, keep it classy 
).
What confused the issue is that I grabbed the command that Bitdefender to setup and launch Rescue Mode and running it from an elevated command prompt because it didn't seem to modify the BCD store at all on the UEFI installs. Using BCDEdit I manually added the entry necessary to boot Rescue Mode (effectively creating a dual boot which Bitdefender does not recommend) and Rescue Mode still did not work. So whether the BCD store is being updated or not the system still does not boot in Rescue Mode. I grabbed EasyBCD and installed a quick Linux distro that uses the same type of BCD entry to boot (Real-mode Boot Sector) and it also doesn't boot so (assuming that was a valid test) I'm focused on UEFI. I don't see why UEFI would keep the BCD from being modified so I think it's a red herring and possibly a flaw in my attempts to collect data.
That's where I left off. At this point I'm focused on UEFI vs BIOS. I'm not the smartest guy in the room and usually consider myself one of the hammers in the bag. I only have a light understanding of many of the things I mentioned, but I'm technical and curious and hope this helps Bitdefender resolve my problem and hopefully someone else's and make a better product for everyone. For the older PC I originally needed to scan (Mom's) the Rescue CD wouldn't work and I had to do almost as much work to come to the conclusion that I was not going to be able to resolve the "needs 1024" video resolution issue and ran a different product. I don't expect that issue on my two PCs where Rescue Mode doesn't work but I'd rather use the current tools for some unknown, stubborn reason.
Thanks for any suggestions and I'll put on my fireproof pants if you want to unload on this. I consider myself stuck until I come up with any more half-backed ideas so I appreciate any assistance. At this point my question is how a UEFI install of Windows could interfere with booting up an alternate OS when the Laptop is set to UEFI/BIOS with bios as preferred.
Edit: This info was sent to support for my ticket.
