The install of the loader went fine. There were no errors reported in the install. I was/am not aware of the error log file. Where might I find it? cheers
If you run the program, expand the O7 window by clicking the "Show Windows 7 Activation Station", then click the "Click here for more options" button. Now go to the "Misc." tab and click on the "View Open 7 Activator's Error log file" link. If the installation went fine as you say, then there may be no error... You may just have a very odd setup as you say. How are your drives/partitions laid out? I assume you have no OEM partition (if your disks were pre-formatted prior to installing Windows 7)?
does anyone have any advice concerning how I might go about activating a copy of Windows 7 in a virtual machine? specifically VirtualBox? None of the loaders or activators I've tried will work. The Open 7 activator gives this error: Code: -----Begin error report----- [2009/12/11 上午 11:34:11] Open 7 Activator Error: Attempted to perform an unauthorized operation. Open 7 Activator encountered an unexpected error while attempting to gain full control access rights to the 'bootmgr' file on the 'SystemVolume'. (See: InstallGRLDR_WO_Mounting(3)) Switching installation method to the alternate method. The 'SystemVolume' will be mounted and the install will continue without interrupt... Loader Method Attempted: bootmgr Attempted Loader Destination: \\.\Volume{7f86d873-e594-11de-9ba2-806e6f6e6963}\\bootmgr Temp Folder Used to Extract Internal Resources to: C:\Users\simon\AppData\Local\Temp\bootmgr Edition of Windows: Windows 7 Ultimate [x86] -----End of error report----- [Version: 1.1.7] -----Begin error report----- [2009/12/11 上午 11:34:12] Open 7 Activator Error: Access to the path 'E:\GRLDR' is denied. Open 7 Activator encountered an unexpected error while attempting to install the loader. (See: Button1_Click(5)) Edition of Windows: Windows 7 Ultimate [x86] Installation Failed at: 4,000% Attempted Product Key/Certificate Installation Method: SLMGR.VBS Attempted Loader Type: bootmgr Is there a way to fix this error? Will Open 7 activator work on an installation in a VM anyway, even if I can get past this error? cheers for any suggestions
The error is a result of you attempting to modify files on your system volume and it is locked for some reason. The loader, being run as administrator, is attempting to gain full access to the 'bootmgr' file in the first error, and the OS is disallowing this for some reason (could be due to your VM). The second error is a write error while trying to write the GRLDR file to the mounted system volume (E: on your PC apparently). It is failing because, again, your OS (or something do do with the VM) has your system partition locked and O7A is unable to gain full access to the drive. If you will notice, in the first error message O7A attempted to use a GUID path to modify 'bootmgr' and was denied due to restrictions present in the OS under your VM, and the second was there because O7A could not gain full write access with a GUID path, so it mounted your system volume in hops of gaining full write access...and was denied both times. Therefore, activation failed because on both occasions O7A could not get full access to your system volume. I would recommend modifying your access privileges/rights for your system volume (you probably will have to mount it first) so that a loader can gain full access to it so the loader file can be installed... EDIT: This is not a problem with O7A, this is a problem specific to your system and your VM unfortunately, and you need to do some troubleshooting and read up on possible problems and solutions that others may have tried in cases that were similar. IMHO, it seems as though your system volume is locked. A search may yield more pertinent results.
Posted new version of O7A in OP. *1.1.8: ---Added a link in the "Misc." tab of the "More Options..." window to allow the user to easily open up the 'keys.ini' file for viewing/editing in Notepad - with 1 click. ---Added option to main O7A form to let user install just the Windows product key (and nothing else). Useful for those of us who just like to update their product key to a more recently leaked one every once in a while... ---Minor updates to code and user friendly enhancements. ---Updated help documentation.
thank you for this, activated my old dell no problem. (after reinstalling due to a different laoder failing) very nice help file/guide too.
Thank you for the feedback, that way I know that it is working well for people. Enjoy your activated Windows
No, I did not add any silent switches... It would be very very easy to do, but I decided against it for the time being. Adding silent switches so people can use the program for pre-activated DVD installations gets more into the realm of 'genuine' software counterfeiting...and I am already pushing it as it is. Maybe sometime in the future I will if enough people request it...
i normally find something when i test my apps then i see if any other apps have the same problem on error resume next works on my app doing the same thing yours does i guess. but i dont know why it would break do you change the picture box image when your click the button? that was my problem then i had to tell it to make a new bitmap and the null reference exception went away
No, I dont modify the form. The button just opens the registry key, checks for any subkeys, then deletes them. I even threw on "on error resume next" in there just in case... *shrug* Oh well, I just threw a few try-catch statements in there instead.
ok well now the new issue is the form wont close i put my info back in and had your app uninstall it and it doesnt close any more. when it happened i told the app to uninstall the info twice. first time worked second time locked the window
if that msgbox is in there i dont get it. i see that msgbox when there is already info installed but when the button is pushed without info i get the jit box
Thanks for your reponse, hotcarl. I got it working in the end by installing Windows 7 *without* a reserved volume, and then using Daz's loader. It seems others have had difficulties accessing system under VirtualBox, too. thanks for all your work on this - keep fighting the good fight