How to Uninstall and Remove OEM BIOS Emulation Driver Activation Exploit/Crack
Microsoft calls Paradox OEM BIOS Emulation OEM Toolkit as OEM driver activation exploit. Whatever is the name, the exploit is a Vista activation crack that bypass product activation. Microsoft said the driver program interferes with standard Windows operation, and thus the exploit has to be removed. In fact, Microsoft has rolled out KB940510 detector via Windows Update that scans the system to catch these exploits.
However, the detector yet to be able to automatically remove the exploits found. However, Microsoft provides removal instructions in KB948253 that is similar to uninstallation guide for Paradox OEM BIOS Emulation Toolkit. The removal instructions of Microsoft also reset the WGAER_W (the WGA exploit detector) status.
To remove the OEM driver activation exploit
- Locate the Royal.sys file in the following folder:
Drive:\Windows\System32\drivers
Note Drive represents the drive on which Windows Vista is installed.
- Delete the Royal.sys file.
- Determine whether the following folder exists on the system:
Drive:\Windows\System32\DRVSTORE\royal_*<followed by many numbers>
If it exists, delete the royal_* folder.
- Click Start button, type regedit in the Start Search box, and then click regedit in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
- Locate the following registry subkey, and then right-click it:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OemBiosDevice
- Click Delete to delete this subkey.
- Locate the following registry subkey, and then right-click it:
HKEY_LOCAL_MACHINE\Software\Microsoft\Genuine Advantage\WGAER_W\GenuineInfo
- Click Delete to delete this subkey.
- Exit Registry Editor.
- Restart the computer.
Note that you may need to enable the Show hidden files option, and then disable the Hide Protected Operating System Files option in Folder and Layout Options’ Advanced Settings to view the files required to be deleted. However, before removing or deleting the OEM driver exploit, make sure you have already purchased a license for Vista and has valid product key in order to activate Vista, else your Vista system will be deemed not genuine.
Related Articles
- Remove and Delete TimerStop Grace Timer Activation Exploit or Crack
- Vista OEM BIOS and Grace Period Exploit Activation Crack Detector To Release via WU
- Uninstall KB940510 to Disable SL07-001 and SL07-006 Vista Exploit/Crack Detection
- Bypass Vista Activation with Paradox OEM BIOS Emulation Toolkit v1.0
- How to Uninstall Paradox Vista Activation Crack and Activator
- KB940510 Anti Grace Timer and OEM BIOS Vista Activation Crack Detector Released
- Windows Vista OEM Activation Crack (vstaldr) without Modify or Flash BIOS
- TimerLock Automated Batch Install Script for TimerStop Driver v2a and Windows Vista Activation 2099 Crack
- Windows Vista OEM Activation Crack by Patching SLIC into Motherboard BIOS
- How to Remove and Uninstall Vista Activation Cracks with VOATK Tools
Entries (RSS)
April 18th, 2008 14:30
Actually, this was THE thing which made me move from windoze to MacBook PRO
. One day, Vista told me I’m done with my notebook – it was correct at the end of day, as I didn’t pay for the bogous OS from MS, I tried it a few months instead of my XP, which was a BIG mistake.
Anybody reading this: consider moving to Apple – I never had one, 1 month is over now with my MacBook PRO 17″ and I LOVE IT, just can’t compare it to the stupid Toshiba Satelite with Vista. The HW rocks, the OS is very friendly, TimeMachine does all the backuping for me, everything runs smoothly.
Forget the silly activation and stupid Vista with all those bugs, performance problems etc. You know what? My newest web camera I bought because of Vista (my Philips was not working anymore..) is not working under Leopard, but my old Philips is
. Funny thing.
Peace,
Johannes
March 18th, 2008 09:53
In my country we named “a Portuguese idea” Mr. Kundun. HA HA HA…
March 16th, 2008 21:04
I actually thought that the whole idea of the paradox oem activator was to install it… not to remove it…
Damn, was I wrong or what
March 15th, 2008 07:03
Does MS look only for Royal.sys?
What happens if you rename it for, let’s say, Loyal.sys and correct all the registry entries to reflect this change.
Has anybody tried this?
Will “Loyal.sys” be transparent to Microsoft?