It depends on how one approaches them since most of the world's top experts who give their time in forums won't even look twice at anyone who is not extremely polite and appreciative. Neosmart, authors of EasyBCD, are the world's leading authorities on multi-booting and normally responsive in their forums. Even an obscure virus will have dozens of listsings. There is no record of an EasyRE virus online anywhere. I'm Greg, an installation specialist and 8 year Windows MVP, here to help you.
Now I have Windows 10 running (but cannot boot it in UEFI mode with secure boot on) but Linux is still damaged.ĭoes anyone know how I can undo the damage done to my system by the "EasyRE" virus? (An extremely bad design when a bad battery prevents the OS from booting - but what else can you expect from Itty Bitty Minds.) Then I tried to again turn off fast boot and secureīoot. Once I could get them to divulge the correct battery, I replaced it. Talking with ASUS lead to the conjecture that the problem was caused by the CMOS clock battery. I used the ASUS UEFI BIOS setting program to turn off fast boot and secure boot. While waiting for NeoSmart's mythical support, I only had one OS (Ubuntu and no ability to back anything up - drives were read-only). More than 3 weeks and still no support (despite many more e-mails.) They promised technical support "as soon as possible". (all my external drives and unlocked internal partitionsĪre mounted as read-only.) I immediately asked NeoSmart (the authors of the virus) for technical support. I actually believed the claims on their web-site. But Windows would not boot.įortunately, I have a UEFI dual boot (Ubuntu MATE 18.04 LTS) and Windows 10 home edition (non-functional, not even installable.) When I installed the latest version (10.5 I had been using 10.0 which worked fine) it told me to reboot.
I thought that the problem was with the Paragon Software HFS+ driverįor windows. (I guess they never read the "Code of Conduct" from their CEO. Windows was down for a month with no help what so ever from Microsoft.
I was caught in the Windows 10 Recovery infinite loop.