Program based Windows 7 loader

[Daz]

Windows 7 Loader v1.7.7 (REPACK) (x86 & x64)

Features

• Can be run as a standalone, just move the executable to wherever you like
• Maintain your own list of serials, future or current (comes with allot of preset keys)
• Add your own certificates and SLIC's
• Automatically finds an available drive letter (if required)
• Installer and uninstaller built in as standard
• Checks your Windows version and build before install
• Automatically finds your active boot partition
• Works on all languages
• Works alongside hidden partitions
• Works on Windows 7, Vista and Server 2008 editions
• Support for bios modded users
• Argument support for silent installs
• You can use this tool to activate your Windows 7/Vista ISO by editing setupcomplete.cmd
• Improves Windows 7 boot time on a Mac
• Encrypted SLIC support

Advantages

• Encryption and randomization for your security
• Byte differences - Everyones GRLDR won't be byte for byte the same
• Profile matchups - SLIC, certificate and serial that best suits your system
• Arguments - Can be used to pre-activate your OS
• Uses custom error checking on near every function making the application much more reliable instead of spitting out files and failing
• Frankenbuild checking
• Integrity checking with useful info on screen so the user can verify it
• External Keys.ini support for all OS versions
• External file support for both SLIC's and certificates
• Newer GRLDR versions before other applications, thus a greater chance of a successful activation

In short this is now the only application based loader or loader period that has encryption and some randomization going on to help protect you from MS. And on top of that it's using a much newer GRLDR with some bug's fixed

About:
This application started off as a proof of concept. Everyone at the time I made this was using batch scripts as the back end to their activation techniques and although batch file installation worked it's success rate was poor when compared to my demo application.

The goal of my program at the time was simple, prove that an application can do everything the batch file can do but in a controlled easy to use way with little to no errors. Not only that though but to show that you can display useful system information and options to the user which a batch file simply can't do.

This program to this very day is still the only fully coded API driven application that handles it's own errors and depends on itself. It's the original program based loader and it's arguably the best loader based program to get you activated out right now with over 2 million downloads and counting and a strong fanbase behind it.


Whats the goal of this program?
To activate you in a clean and simple way without putting a load of buttons and checkboxes on your screen and expecting you to know what to do. It's all about keeping it simple!

What makes this different from every other loader out at the moment?
It's the only fully coded API based loader application, this means it cuts out the middle man (.NET framework) and can handle everything on it's own. This increases reliability and is considered the professional coder approach.

So whats the advantages and why should you care?
With me building this loader as an application I can access system details and create declares for many of the functions. This means anyone that uses this loader should have a greater chance of success!

Whats the differences between each loader option?
Each option uses a slightly different method to get you activated, of course the custom menu.lst option should be ignored unless you know what you're doing.

OK so how do I run it?
In general you simply press Install!

I activated Windows 7 and now I want to activate Windows Vista, why isn't it working?
Use the uninstall option while on Windows 7 and reboot into Windows Vista. Next install your selected cert/slic in Windows Vista and then reboot back to Windows 7 and click install.

Activation failed, now what?
Try again with one of the other loader options, maybe one of them might just work for you.

Application integrity checking?
Hover your mouse over the green, amber or red icon towards the bottom right of the window to see the information.

I should note that even if the icon is green someone might have found a way around it so it's worth checking that the applications path is always the same as the location from where you launched the application. You should also check that the MD5 matches the MD5 found online.


Changes since 1.6.9

• 1.7.0 -- Removed the older loader
• 1.7.0 -- Added loader mode options
• 1.7.0 -- Changed the UI so that it's now slightly transparent as well as resized to suit the new options
• 1.7.0 -- Added Samsung support for Windows 7 Ultimate, Professional & Home Premium editions
• 1.7.0 -- Improved internal resources security
• 1.7.1 -- Removed window transparency to fix a Windows 7 artifacts bug and improve responsiveness on older systems using onboard graphics
• 1.7.1 -- Improved the "Custom menu.lst" loader option. It will now show all people using this setting the GRUB menu at system startup
• 1.7.1 -- Upgraded some certificates to version 2.1
• 1.7.1 -- Added a new GRLDR version (0.96) from zsmin (custom edition for my program)
• 1.7.1 -- Added external SLIC support (read "How to add support.txt" for more info)
• 1.7.1 -- Added support for BenQ and Sony machines
• 1.7.1 -- Added support for Windows 7 Starter Edition
• 1.7.1 -- Added various new OEM SLP serials
• 1.7.2 -- Added encrypted SLIC support
• 1.7.2 -- Added random loader names
• 1.7.2 -- Added byte differences (everyones GRLDR loader won't be byte for byte the same)
• 1.7.2 -- Added a new GRLDR version (0.97) from zsmin (custom edition for my program)
• 1.7.2 -- Added /norestart argument
• 1.7.2 -- Added support for Windows 7 Home Basic (4 new keys)
• 1.7.3 -- Improved free drive letter assignment
• 1.7.3 -- Corrected some grammar
• 1.7.3 -- Added random SLIC encryption support, this means everyones SLIC will have a unique encryption
• 1.7.3 -- Added GRLDR file size randomization
• 1.7.3 -- Added GRLDR v0.97-DAZ+SEC-R2. This is just a minor version to support the random encryption
• 1.7.3 -- Added SLIC table detection (BIOS mod and software, it can tell the difference) -- this feature is in BETA
• 1.7.3 -- Added support for Advent, Medion and Nokia
• 1.7.3 -- Added various new OEM SLP serials
• 1.7.4 -- Improved SLIC detection (still not tied to anything, it's simply a BETA feature until I get more feedback)
• 1.7.4 -- Fixed file write errors caused by version 1.7.3
• 1.7.4 -- Added support for Server Standard R2
• 1.7.4 -- Added support for FSC, Quanmax and Trigem
• 1.7.4 -- Added various new OEM SLP serials
• 1.7.5 -- Removed the beta SLIC detection (caused crashes on 1.7.4)
• 1.7.5 -- Added support for LG
• 1.7.5 -- Added various new OEM SLP serials
• 1.7.6 -- Improved the encryption support
• 1.7.6 -- Added Toshiba Professional serial
• 1.7.6 -- Added support for Gigabyte

Latest - 1.7.7

• Fixed loader modes to stop system hangs
• Changed the way the loader is wrote to the partition (no more mounting)

MD5: fb11ad4bfdf3b063ce1116294c8db769
SHA1: 58cbaff2c5473290ceee8c895455df5af140d1c5


Download links (repacked)
slics.myftp.org
multiupload.com

[Daz]

Do I need to update?
If you have installed a version and you're activated then you shouldn't need to update. If however you are like me and you like to use the latest and the best versions of software then updating shouldn't be a problem.

Can I install a newer version over an older version?
Yes, you don't need to perform an uninstall to upgrade to a newer version.

Usage instructions
If you have no SLIC 2.1 in BIOS (which unless you flashed with a modded BIOS, you probably do not have)

1. Install windows 7 (Don't enter a serial during installation)
2. Run this as an Administrator (Should prompt you)
3. Click on Advanced Options (Optional as the program will try to best detect the following for you)
4. Choose a matching SLIC and certificate (Dell, MSI, etc.) (Optional)
5. Choose a loader mode (Optional)
6. Click on the install button (Under software mod)
7. Wait for the Loader to work and reboot.
Enjoy !!!!

Note:
If Windows does NOT activate:
Re-run the loader under Windows and choose a different loader mode from the drop-down list.

[whitehat2009]

Quite frankly, all this talk about "which loader is the best" and "my loader is better than yours" is getting tiring. No loader, no matter how well-coded it is, cannot beat the elegance of a true BIOS mod.

[Hazar]

Im affraid not Hazar, this doesn't depend on size or guessing paths. It uses a system declare which gets the path 100% accurate all the time -- something a batch file can't do

This activates pretty much anything I have tested it on, with or without a drive letter too. It also doesn't hold resources like your own loader, it can generate its own fresh files.

I beg to differ. the batch will search for a 100mb partition, and the system reserved will be 100mb. It will mount every 100mb partition it finds, and unmount when done. 100% reliable.

[TVTVTV]

No loader [...] cannot beat the elegance of a true BIOS mod.

Nor the risk factor, too. Especially in the case of notebooks/laptops.

[bogstandard]

Tells me my version 7232 is not avalid windows version which is positive as of course it is not being a bit of a mongrel

[Daz]

I beg to differ. the batch will search for a 100mb partition, wand the system reserved will be 100mb. It will mount very 100mb partition it finds, and unmount when done. 100% reliable.

Exactly, it will search for it so you get an instant performance hit and theres nothing to say it will always find what its after if the syntax should ever change. With me using declares everything will always remain the same and it will remain reliable, that plus error and UAC handling all within one small excutable.

Using a declare the system simply tells my application the exact active volume we need to write to, simple as that. Plus with mine being an application I can further design the UI to hold more serials and/or information about your OS.

[Daz]

Tells me my version 7232 is not avalid windows version which is positive as of course it is not being a bit of a mongrel

It will only activate Ultimate RTM 7600.

[Daz]

Quite frankly, all this talk about "which loader is the best" and "my loader is better than yours" is getting tiring. No loader, no matter how well-coded it is, cannot beat the elegance of a true BIOS mod.

I do agree with you, mines modded myself. This loader is just something I done because I was (a) bored, (b) to help others & (c) Hazar said it couldn't be done so easy and well... I done it lol

It's not that I think this loader will go down as the best either, its just the only one thats program based and is really simple to use.

[Hazar]

Exactly, it will search for it so you get an instant performance hit and theres nothing to say it will always find what its after if the syntax should ever change. With me using declares everything will always remain the same and it will remain reliable, that plus error and UAC handling all within one small excutable.

Using a declare the system simply tells my application the exact active volume we need to write to, simple as that. Plus with mine being an application I can further design the UI to hold more serials and/or information about your OS.

Well Daz it sounds like a cool way of doing things, but to be honest there is no performance hit because all you are doing is doing something for every occurance of something in a small text output. I have made a UAC manifest for my VB.net app as well. Cool idea though.