I have for over 1 year a stable working PC with "Windows 10 Home" on 64bit.
I downloaded 2 days ago Panda Cloud Cleaner from here http://www.pandasecurity.com/romania/su ... eusers.htm (the installer, NOT THE PORTABLE ONE).
Its version is 1.1.8.
After I made a normal scan, I went to Advanced Options and tick "Activate Trusted Boot".
There should be 3 boots, like the program said, but after the first succesfull boot, the second boot stuck my Windows10 in a Startup Repair Infinite Loop (its a known error)
So I cant boot into windows at all!
Things I tried to repair it (failed so far):
- made a DVD with Windows 10 (bootable)
- I disabled Windows 10 Automatic Startup Repair in command prompt like this:
bcdedit /set {default} recoveryenabled no
- in command prompt I typed "bcdedit" and I saw how my partition name was strangely changed to "D:" from "C:" (after the Panda Trusted Boot, ofc). I had ONLY ONE PARTION ON MY SSD, THE PARTITION C:.
- I renamed the partition with command prompt like this :
C:\> bcdedit /set {default} device partition=C:
C:\> bcdedit /set {default} osdevice partition=C:
- I tryed to repair the boot with these command lines in cmd:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
- after "bootrec /rebuilddbc", the partition named was changed back again with "D:", BUT I DONT HAVE A D: PARTITION, ONLY C: !!!
- I deleted the installation folder for Panda in C:\Program Files (x86)\Panda Security\Panda Cloud Cleaner (I have a second PC, so I can put my harddrive and deleted from there
- I deleted ALL related Panda ".SYS" files from C:\Windows\System32\drivers
So, after each change the result was the same, a BSOD with the same mesage for the missing or corrupt file: winload.exe
But "winload.exe" exists in the C:\Windows\System32. Its THERE. All bootable files are at their places, so my guess is Panda Cloud Cleaner made a virtual boot place or something, somewhere, and messed up with windows 10 boot.
I read this article http://www.pcmag.com/article2/0,2817,2423721,00.asp and the author said "
"This isn't too uncommon a behavior in emergency cleanup tools; they use more aggressive cleanup techniques than standard antivirus. However, in one case this overactive cleanup rendered the test system unbootable. Panda's developers went into overdrive and soon supplied me with a one-off rescue CD to fix the problem. It succeeded, but I wonder if the ordinary user would have gotten such service... Cons: Scan rendered one system unbootable. After fix by tech support, trusted boot scan rendered that same system unbootable again; again solved by tech support...
And I know now Panda Trusted Boot is only for 32bit (if i understand correctly) it shouldnt work on 64, but how it could worked on 64bit in my case????? This is not my fault!
I dont know what to do, PLZ HELP!!!!