Hello Jadedea,
This would be from an unsigned driver. You can use the File Signature Verification tool to navigate to the folders where you want to test the driver files (ex: "C:\Windows\System32\Drivers") to see what drivers are not signed.
When you find them, you can uninstall them.
Hope this helps for now, :)
Shawn
Brink,
Thanks for the tip. Ran the verifier with the log and it looks like this: difxapi.dll is the unsigned driver. I will see if I can run system repair and chose the install driver option unless you know of an easier way.
Thanks again!
The difxapi.dll file is for "Driver Install Frameworks for API library module".
Since this is a system file, running a sfc /scannow command may be able to sort it for you. :)
Ok I tried using system repair load drivers and I could not find the driver. I looked up the driver and found 29 versions of it. Is that normal?
I was able to follow the tutorial to successfully remove the watermark. I was running in unsigned driver mode to try and get Desktop Heap Monitor to work for Windows 7. However since I have BitLocker on my drive, every time I start my computer I get a warning that the Boot Configuration Data (BCD) has changed and asks me for the BitLocker recovery key every time. I don't want to suspend and resume BitLocker to make the configuration changes the new defaults. Could anyone help with the commands to undo the configuration changes? I didn't want to randomly try things that might further change the boot configuration. I am assuming the opposite commands might be something like:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Please let me know if this is correct. Thanks.
Hi thanks for your reply. I was still getting the BitLocker screen with the codes 0x12000030 and 0x16000048 which I found meant loadoptions and testsigning BCD Settings and BitLocker were still being recognized as changed settings. I ended up having to
bcdedit.exe /deletevalue {current} loadoptions
bcdedit.exe /deletevalue {current} testsigning
since it turns out those values were not set before. Now I don't have the annoying BitLocker screen anymore. Thanks
Quote