R
RayLopez99
Strictly as an academic exercise I'd like to try and mount this .iso I downloaded from a legal site and follow the below instructions. But there's somuch information I'm confused a bit.
How to make sense of it? I can understand most of it, but there's a lot ofstuff going on that does not make sense.
My trial setup is to use an emulator (virtual OS) and after I burn the .isoI figure that you'll have to then enter a key (within 30 days) to 'activate' the Windows 7. If you read the below the implication is that there are several ways to avoid the annoying nag screen or limited functionality thatcomes with Windows that is not activated. The ways include three modes:
Q: What changes bring in process of loading Windows for UnSafe, Safe and Safest emulation modes?
A:
Safest - the activator loader calls Windows.
Safe - the activator loader calls the original boot loader.
UnSafe - the boot sector calls the activator loader, the activator loader calls the original boot loader
I don't understand what "activation loader" is--but I reckon it is a shell that calls Windows. Note it is not the "original boot loader", which is deemed the "unsafe" mode (meaning it's likely to be blocked by Microsoft in the sometime immediate future for Windows updates once a lot of people startusing it--at least that's what I think it means). So the "activator loader"--which in theory can be a rootkit virus--calls Windows and somehow givesit a legal activation key each time, and without destroying whatever user data the user has on their hard drive (like in user/MyDocuments), is that it?
Any advice appreciated. I plan on using this .iso for experimental software just to test the same, not for any personal uses that contain my personalinformation, so I really don't care if there is a rootkit virus on the "activation loader".
I also include some information on SLIC I found on the web.
What are these loaders? Which one is 'best', which one is used by this package?
Installs/Uninstalls/Detects public SLIC emulators:
- W7 Loader
- Open W7 Loader
- SLIC Driver
- Vista Boot
- WOW7 Loader
- MBR SLIC Loader
- Vista Loader
What is KMS Activation? From this: "KMS servers" I take it to mean that ifyou plan to use this .iso forever, you can periodically, from I suppose some hacker site, download fake Windows keys that will allow you to run Windows to get Windows 7 updates--is that it? The KMS servers reside on the hacker's site, is that it? That must be it. I recall using such an .iso on aVista machine I had--it worked fine for about a year, and I was able to get updates, until one day one of those updates had a "Check to see if you are running Genuine Windows" module and I got a notice saying I was running an unauthorized version of Windows along with a periodic nag screen. Once Ipaid up Microsoft, I got a legal key and all was well again. So I guess this KMS Activation is way of constantly downloading unauthorized keys to avoid having to pay Microsoft, is that it?
RL
*** from the README.TXT file ***
Windows 7 Loader eXtreme Edition
Activates all Windows 7 versions:
Ultimate, Professional, Enterprise, Starter, Basic, Home, etc.
Activates Windows 7 / Vista / 2008 R2 / 2008 - RTM / preRTM / Office 2010
Supported editions: All
Back up your tokens.dat file if you must have a version other than Ultimate..
This activator is a 'Franzenfuilde' Loader, meaning it swaps out files in order to activate.
Features:
- Safer loader installation (than other activators)
- Activate any edition (without reducing default activation abilities)
- Trial Reset (get back 4 rearms and 30 days)
Installs/Uninstalls/Detects public SLIC emulators:
- W7 Loader
- Open W7 Loader
- SLIC Driver
- Vista Boot
- WOW7 Loader
- MBR SLIC Loader
- Vista Loader
KMS Activation:
- Emulated KMS Server
- Internet KMS Servers
Download latest updates(w7lxe.exe /update):
- Windows 7/Vista/2008R2/2008 keys
- Windows 7 SLICs
- Windows 7/Vista Certificates
- W7 Loader
- Open W7 Loader
- SLIC Driver
- MBR SLIC Loader
- KMS Emulator
- Activate any editions
- Automatic and Advanced Mode
- Complete loaders collection
- Custom loaders integration
- Windows activation information
- SLIC checking: checksum, SLIC&RSDT&XSDT markers
- Installed loader information: Boot Loader and SLIC Emulator
- Installed key information
- SLIC dump
- Certificate dump
- Product key checker
- Logos and OEM information installation
- Commmand line keys
- Internal SLIC's storage
- Internal Certificates storage
- Ability to use external SLIC's storage
- Ability to use external Certificates storage
- SLIC and Certificate comparison
- Custom KMS servers list
- Custom keys list
- Custom logos list
KB971033 ready.
Shows extended activation-related information.
Detects Chew-WGA&RemoveWAT-related system changes.
Activates Office 2010 (w7lxe.exe /office2010).
Emergency recovery
MBR SLIC Loader and "Sleep Mode" compatibility:
"Clear CMOS" jumper.
NOTES:
Default SLIC emulator: W7 Loader (Forceful)
Default emulation scheme: Safest + UnSafe
1. "Safest" uses Loader with Vista Boot Loading Screen (with option to use original W7 in boot options)
2. "Safe" uses Loader with W7 Boot Loading Screen (with option to use original W7 in boot options)
3. "Unsafe" uses Loader with W7 Boot Loading Screen (no option to use original W7 in boot options)
-----------------------------------------------
Vista type boot screen after installing loader?
Try uninstalling the loader and install with "Safe" or "Unsafe" mode checked.
-----------------------------------------------
Special abilities:
- Trial Reset (get back 4 rearms and 30 days)
- Windows is always has recovery option (not need to recovery from DVD if SLIC emulator crash PC)
- Activate any edition w/o reducing default activation abilities
-----------------------------------------------
Accessibility:
- Reset Trial (returns 4 rearms and 30 days)
- Windows always has the option to restore the work (no need to restore from the DVD, if your computer can not boot after the application of SLIC emulator)
- Activates any editor without loss of activation opportunities
-----------------------------------------------
New command line keys:
w7lxe.exe / biosbootmenu
- Prevent activation drop for BIOS boot menu (Multi-boot)
-----------------------------------------------
It does work and will activate all Win 7 editions.
But…
Windows 7 Loader extreme Edition 3 uses retail MSDN keys, this is misleading as it combines them with certs in the UI, making it look like an OEM key.
When the keys reach their maximum activation limit or Microsoft blocks them, this will become useless, unless Nabalum has an unlimited supply of MSDN keys.
Back up your tokens.dat file if you must have a version other than Ultimate..
FAQ:
Q: I the novice user of the PC, saw that there are various activators Windows 7 Loader. What of them to select?
A: To beginners and those who not ready to restore the loader, owing to impossibility to boot after application of activators, it is recommended to use only safe Windows 7 Loader extreme Edition v3. If the "Loader" method used then press "Cancel" button after reboot.
Q: How to use the activator?
A: Start w7lxe.exe, do nothing, wait when all makes the activator in an automatic mode.
Q: Online genuine validation shows the error.
A: KB971033 is blocked for the purpose of preventing possible activation loss in the future.
Q: Can't Microsoft begin to ban modified BIOS with SLIC 2.x?
A: Yes, it is theoretically possible. In Windows Vista times loaders banning was just theory too.
Q: What emulation mode is used by default?
A: Safest emulation is used for SLIC emulator check. If SLIC emulation and activation has passed successfully than UnSafe emulation.
Q: For me it was not initial the load menu and delay time for boot menu but why after application of the "Loader" method there is 30 second return counting?
A: Such occurs only at the first reboot what in case if the SLIC emulator does not work (black screen) it was possible to reboot and use the native choice Windows 7. Other activators, in the case if the SLIC emulator does notwork, it demands to restore procedure with installation DVD usage.
Q: I do not wish to use illegal keys and KMS servers, but thus I wish to have to have "genuine software" status. What can recommend?
A: Use the grace period. For limitation overcoming on the maximum period ofusage (4x30=120 days) to apply the "Trial Reset" method to reset of counters:
w7lxe.exe->Trial Reset->Activate
or
w7lxe.exe /method=TrialReset
Q: How to restore system after unsuccessful usage of TrialReset method by 3..115-3.118 version?
A: Run
w7lxe.exe /trial-recovery
from different windows 7 or Windows Vista installation.
Q: I wish to make on Windows 7 and Windows Vista 49516 grace days the "49516 Trial Days" method as a constant working solution of a question about activation.
A: It is not necessary to make such choice as a constant basis. With the advent of the "Trial Reset" method the such solution has lost sense. Though for Windows Server 2008R2/2008 it is quite applicable. The "49516 Trial Days" method now has more likely fact-finding character that such is possible.
Q: After application of the "Loader" method activation does not occur. Whatto do?
A:
1) Advanced Mode->Boot Loader->Install
2) Reboot
3) Advanced Mode->Upload Screenshot
Or keyboard->PrintScreen; Run->MsPaint->Paste->Save; http://imageshack.us/->Browse...->start upload
4) Ask advanced users for help, having placed a screenshot.
Q: Used the "Loader" method, after rebooting the activator choice (Windows 7 Loader XE) does not load Windows. It was necessary to take advantage of the original choice.
A: It most likely means that the SLIC emulator used by default does not work on the given computer.
Try other emulators (it is necessary to reboot each time):
Advanced Mode->Boot Loader: MBR SLIC Loader->Install
Advanced Mode->Boot Loader: Vista Boot 08.0501->Install
Advanced Mode->Boot Loader: Vista Loader 2.1.2->Install
Advanced Mode->Boot Loader: WOW7 Loader->Install
Advanced Mode->Boot Loader: W7 Loader (Default)->Install
Advanced Mode->Boot Loader: W7 Loader (Alternative)->Install
Advanced Mode->Boot Loader: W7 Loader (LowMemory)->Install
Advanced Mode->Boot Loader: SLIC Driver->Install
Q: How to change delay time for boot menu?
A: Advanced Mode->Boot Loader->timeouts
Q: In what advantage Safest emulation?
A: Always there is a possibility after rebooting to load Windows that is important when the SLIC emulator does not work. Safe emulation should gives the such possibility too.
Q: At start the activator shows the message that it supports only FAT and NTFS file systems.
A: It is possible to skip compulsorily the check of the file system and to start the activator:
w7lxe.exe/fscheck=off
Or for preventing from undesirable effects:
w7lxe.exe/fscheck=off/bootsect=off /mbr=off
- In these two variants UnSafe emulation does not work.
Q: In the list of warnings it is written: "Loader: SCSI boot device detected!". What consequences can occur owing to application of the "Loader" method?
A: Warnings specify in the reason there can not pass activation. In this case SLIC emulation will probably not work.
If the emulator has not worked, in such situation it is necessary to try:
Advanced Mode->Boot Loader: Vista Boot 08.0501->Install
Advanced Mode->Boot Loader: SLIC Driver->Install
Q: In the list of warnings it is written: "Incomplite SLIC(OEMX) detected!"..
A: It is necessary to try:
Advanced Mode->Boot Loader: MBR SLIC Loader->Install
Q: How the automatic mode of the activator works? How it makes a choice of a method for the recommendation?
A: If for the installed edition Windows exists OEM:SLP key and SLIC is detected - the "Certificate" method is recommended.
If SLIC is absent - the "Loader" method.
If for the installed edition of Windows does not exist OEM:SLP key - the "180+ Days" method.
Thus all line of editions Windows 7/Vista/2008R2/2008 becomes covered (Except N and E editions which can be activated by self-decision). if Windows marked as "Pirated" Or other methods are not applicable - than "Trial Reset" method.
Q: What sequence of operations corresponds to the "Loader" method in the automatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: OEM:SLP (OEM) Key->Install
2) Advanced Mode->Key AND Certificates->Certificate->Install
3) Advanced Mode->Boot Loader->Install
4) Reboot
If SLIC emulation and activation has passed successfully:
5) Advanced Mode->Boot Loader->Emulation: UnSafe->Install
6) Reboot
Q: What sequence of operations corresponds to the "180+ Days" method in theautomatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: Volume:GVLK (Volume) Key->Install
2) Advanced Mode->KMS Activation->Activate
Q: What sequence of operations corresponds to the "Certificate" method in the automatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: OEM:SLP (OEM) Key->Install
2) Advanced Mode->Key AND Certificates->Certificate->Install
Q: I has bought a new computer how to extract all information linked to activation?
A:
1) Advanced Mode->Windows->Dump (Certificate) - keeps the certificate
2) Advanced Mode->BIOS->Dump (SLIC) - saves SLIC
3) Product Key Info->Product Key - shows the installed key
Q: How to return the Windows 7 boot screen and the hibernation mode if 3.011-3.014 version has been used?
A:
1) w7lxe.exe->Loader->Deactivate
2) Reboot
3) w7lxe.exe->Loader->Activate
Q: Activated, but activation is lost each time after hibernation.
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
or
bcdedit -store \boot\lxe ...
Q: For me it is installed Windows XP and Windows 7. After activation there was a third choice "Windows 7 Loader XE". Whether it is possible to delete the native choice Windows 7?
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
Or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
- the such solution is preferable.
Q: It is necessary to customize loading Windows through bcdedit, in particular bcdedit-set testsigning on and HASP driver does not work.
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
Or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
Q: At loading computer there is a flashing menu. How to remove the flashingor the menu?
A: Advanced Mode->Boot Loader->Emulation: UnSafe->Install
Q: I wish to activate at once through UnSafe emulation. Whether it is necessary so to do?
A: No, it is recommended to pick up in the beginning the working SLIC emulator, with which Windows is activated.
After that it is possible to install through UnSafe SLIC emulation, with the big share of probability, it will work without complications.
Q: I use... (Something like a virtual file system) for disk image creation in real time. It boots before Windows - I am afraid to use the "Loader" method.
A: In an automatic mode (Safest emulation) usually the boot sector and the boot loader are not rewritten.
What to prevent those exclusive situations in which the activator all the same rewrites boot sector, it is possible to use the command line key:
w7lxe.exe/bootsect=off /mbr=off
Q: What physical changes bring in system for UnSafe, Safe and Safest emulation modes?
A:
Safest - changes mention only the boot menu.
Safe - changes mention only the boot loader.
UnSafe - changes mention boot sector and the loader.
Q: What changes bring in process of loading Windows for UnSafe, Safe and Safest emulation modes?
A:
Safest - the activator loader calls Windows.
Safe - the activator loader calls the original boot loader.
UnSafe - the boot sector calls the activator loader, the activator loader calls the original boot loader.
Q: In what emulation mode (UnSafe, Safe, Safest) other activators Windows 7Loader work?
A: UnSafe
Q: I have a legal MSDN key for edition distinct from that which is installed, Windows refuses to accept it.
A: Advanced Mode->Key AND Certificates->Key: Retail (MSDN) Key->Install
Q: How the activator allows installing keys of editions distinct from that which has been installed?
A: Such it is possible thanks to existence of the internal mechanism Windows "Anytime Upgrade". Direct interaction of the activator with it allows notbreaking functioning of the activation mechanism (in difference of other "universal" activators).
Q: How to get the information about the new key?
A: Advanced Mode->Key AND Certificate->Key->Get Info
Q: Where to learn what keys of the command line and external files support the activator?
A: Advanced Mode->Windows 7 Loader XE->Info
Q: Where to learn the detailed information about Safest, Safe, Unsafe emulation?
A: The scheme in archive: Info\w7lxe-emu1-3300.png
//
SLIC what it is how it works overview
Just some shamelessly stolen cut and pasted basic overview info for so many newbies like myself learning just what SLIC is and how it works. This first part covers SLP 1.0.
We are all fairly much aware of how SLP 2.0 works under Vista: The BIOSof an OEM computer has a special ACPI Table called a Software Licencing (SLIC) table which identifies the machine, a special certificate is installedon the computer which validates the SLIC table and authorizes the installation, and a Royalty OEM serial key is used to identify the version of Windows installed. When all three components are installed, the system self-activates.
Under Windows XP, SLP also exists, but in an earlier version (SLP 1.0).this system works similarly to the version used by Vista in that it uses aBIOS component to identify the machine as an OEM manufactured one, a groupof files to validate the BIOS and authorize the installation, and a serialkey to allow the installation of the desired OS.
However, the similarity between SLP 1.0 and SLP 2.0 ends there.
One of the biggest differences is that the BIOS component of SLP 1.0 isnot a SLIC table. Instead, it is a simple text string stored at some specifc location within the BIOS DMI data area. No encryption or fancy algorithyms are used to hide this string. However, some OEM machines do go a step further and calculate checksums on multiple blocks within the BIOS to identify the machine.
While the BIOS component is much simpler under SLP 1.0, the opposite istrue of the validation file. Instead of using a certificate which is compared through an encryption algorithm to the BIOS component, the SLP used by XP requires a series of four files containing an active scanning and validation program that is used to authenticate the installation. These files allhave the name OEMBIOS but a different extension and can be found within the i386 folder of the XP installer CD. (The files are installed to the Windows\System32 folder of the XP installation, as well.)
As for the installation key, all SLP 1.0 keys are manufacturer specific.. A Dell OEM installation cannot use an Acer CD key, for example. This is different from SLP 2..0 where the Installation keys are common to all manufacturers.
A program such as an emulator to make XP think it is an OEM machine is not possible under SLP 1.0, as the validation routine actually scans the existing BIOS ROM chip.
While an emulator cannot be had, modifying the system to use SLP 1.0 isvery simplistic. A common program called a DMI Editor will allow you to modify the DMI configuration data to insert the required string into a non-OEM board. On most OEM systems, this is nothing more than the name of the manufacturer embedded in the DMI data as the System Manufacturer.
(Some OEM machines use further validation, requiring that multiple blocks of memory in the BIOS chip match what the original machine's BIOS contained. Since this would require severe modification to the BIOS program code to achieve, most people simply ignore these OEM brands altogether.)
What string you must insert depends on what OEMBIOS.* files you have onyour installation CD. Several sites have are around which both host the OEMBIOS files and provide the specific details of the correct manufacturer's string and how to edit it. Using those OEMBIOS files, you can easily modifya regular XP home or Pro CD into an OEM one - merely by copying the files over and embedding the correct serial key.
and from MS....
System Locked Preinstallation, often abbreviated as SLP, is a procedureused by major OEM computer manufacturers in order to preactivate Microsoft's operating systems Windows XP, Windows Server 2003 and Windows Vista before mass distribution. Operating systems that use SLP check for a particulartext string in a computer's BIOS upon booting. If the text string does notmatch the information stored in the particular installation's OEMBIOS files, the user is prompted to activate his or her copy as normal. This effectively "locks" the operating system to the qualified motherboard. In addition, if an end user feels the need to perform a "clean install" of Windows, and if the manufacturer supplies the user with an installation disc (not a "System Recovery" disc that is a hard drive image), the user will not be prompted to activate the copy, given that the installation is performed on the same motherboard. Furthermore, because the check only involves the BIOS andnot hardware, a user is allowed to change virtually all hardware components within the machine, a procedure that would normally trigger re-activationin retail XP/Server 2003 copies.
It is important to note that SLP installations still require a product key, which are unique to the specific version of Windows (Home, Professional, Server, etc...). The product key printed on the Certificate of Authenticity affixed to an OEM assembled computer will usually suffice. As of February 28, 2005[1], those keys were invalidated for normal activation by Microsoft in an effort to further reduce software piracy, but does not apply to SLP. If the COA product key is lost, then product key finders, readily available on the Internet, can decrypt the key from a local installation. Keys from either source will allow the user to avoid activation upon reinstallation. Also, Microsoft released the following generic product keys that can beused to avoid product activation on any SLP-enabled computer using the corresponding version of Windows XP:
(Please note that the following keys are not volume license keys. The installation source must also be SLP-enabled by the manufacturer.)
Windows XP Professional (32-bit)
Windows XP Professional (64-bit)
Windows XP Tablet PC Edition
How to make sense of it? I can understand most of it, but there's a lot ofstuff going on that does not make sense.
My trial setup is to use an emulator (virtual OS) and after I burn the .isoI figure that you'll have to then enter a key (within 30 days) to 'activate' the Windows 7. If you read the below the implication is that there are several ways to avoid the annoying nag screen or limited functionality thatcomes with Windows that is not activated. The ways include three modes:
Q: What changes bring in process of loading Windows for UnSafe, Safe and Safest emulation modes?
A:
Safest - the activator loader calls Windows.
Safe - the activator loader calls the original boot loader.
UnSafe - the boot sector calls the activator loader, the activator loader calls the original boot loader
I don't understand what "activation loader" is--but I reckon it is a shell that calls Windows. Note it is not the "original boot loader", which is deemed the "unsafe" mode (meaning it's likely to be blocked by Microsoft in the sometime immediate future for Windows updates once a lot of people startusing it--at least that's what I think it means). So the "activator loader"--which in theory can be a rootkit virus--calls Windows and somehow givesit a legal activation key each time, and without destroying whatever user data the user has on their hard drive (like in user/MyDocuments), is that it?
Any advice appreciated. I plan on using this .iso for experimental software just to test the same, not for any personal uses that contain my personalinformation, so I really don't care if there is a rootkit virus on the "activation loader".
I also include some information on SLIC I found on the web.
What are these loaders? Which one is 'best', which one is used by this package?
Installs/Uninstalls/Detects public SLIC emulators:
- W7 Loader
- Open W7 Loader
- SLIC Driver
- Vista Boot
- WOW7 Loader
- MBR SLIC Loader
- Vista Loader
What is KMS Activation? From this: "KMS servers" I take it to mean that ifyou plan to use this .iso forever, you can periodically, from I suppose some hacker site, download fake Windows keys that will allow you to run Windows to get Windows 7 updates--is that it? The KMS servers reside on the hacker's site, is that it? That must be it. I recall using such an .iso on aVista machine I had--it worked fine for about a year, and I was able to get updates, until one day one of those updates had a "Check to see if you are running Genuine Windows" module and I got a notice saying I was running an unauthorized version of Windows along with a periodic nag screen. Once Ipaid up Microsoft, I got a legal key and all was well again. So I guess this KMS Activation is way of constantly downloading unauthorized keys to avoid having to pay Microsoft, is that it?
RL
*** from the README.TXT file ***
Windows 7 Loader eXtreme Edition
Activates all Windows 7 versions:
Ultimate, Professional, Enterprise, Starter, Basic, Home, etc.
Activates Windows 7 / Vista / 2008 R2 / 2008 - RTM / preRTM / Office 2010
Supported editions: All
Back up your tokens.dat file if you must have a version other than Ultimate..
This activator is a 'Franzenfuilde' Loader, meaning it swaps out files in order to activate.
Features:
- Safer loader installation (than other activators)
- Activate any edition (without reducing default activation abilities)
- Trial Reset (get back 4 rearms and 30 days)
Installs/Uninstalls/Detects public SLIC emulators:
- W7 Loader
- Open W7 Loader
- SLIC Driver
- Vista Boot
- WOW7 Loader
- MBR SLIC Loader
- Vista Loader
KMS Activation:
- Emulated KMS Server
- Internet KMS Servers
Download latest updates(w7lxe.exe /update):
- Windows 7/Vista/2008R2/2008 keys
- Windows 7 SLICs
- Windows 7/Vista Certificates
- W7 Loader
- Open W7 Loader
- SLIC Driver
- MBR SLIC Loader
- KMS Emulator
- Activate any editions
- Automatic and Advanced Mode
- Complete loaders collection
- Custom loaders integration
- Windows activation information
- SLIC checking: checksum, SLIC&RSDT&XSDT markers
- Installed loader information: Boot Loader and SLIC Emulator
- Installed key information
- SLIC dump
- Certificate dump
- Product key checker
- Logos and OEM information installation
- Commmand line keys
- Internal SLIC's storage
- Internal Certificates storage
- Ability to use external SLIC's storage
- Ability to use external Certificates storage
- SLIC and Certificate comparison
- Custom KMS servers list
- Custom keys list
- Custom logos list
KB971033 ready.
Shows extended activation-related information.
Detects Chew-WGA&RemoveWAT-related system changes.
Activates Office 2010 (w7lxe.exe /office2010).
Emergency recovery
MBR SLIC Loader and "Sleep Mode" compatibility:
"Clear CMOS" jumper.
NOTES:
Default SLIC emulator: W7 Loader (Forceful)
Default emulation scheme: Safest + UnSafe
1. "Safest" uses Loader with Vista Boot Loading Screen (with option to use original W7 in boot options)
2. "Safe" uses Loader with W7 Boot Loading Screen (with option to use original W7 in boot options)
3. "Unsafe" uses Loader with W7 Boot Loading Screen (no option to use original W7 in boot options)
-----------------------------------------------
Vista type boot screen after installing loader?
Try uninstalling the loader and install with "Safe" or "Unsafe" mode checked.
-----------------------------------------------
Special abilities:
- Trial Reset (get back 4 rearms and 30 days)
- Windows is always has recovery option (not need to recovery from DVD if SLIC emulator crash PC)
- Activate any edition w/o reducing default activation abilities
-----------------------------------------------
Accessibility:
- Reset Trial (returns 4 rearms and 30 days)
- Windows always has the option to restore the work (no need to restore from the DVD, if your computer can not boot after the application of SLIC emulator)
- Activates any editor without loss of activation opportunities
-----------------------------------------------
New command line keys:
w7lxe.exe / biosbootmenu
- Prevent activation drop for BIOS boot menu (Multi-boot)
-----------------------------------------------
It does work and will activate all Win 7 editions.
But…
Windows 7 Loader extreme Edition 3 uses retail MSDN keys, this is misleading as it combines them with certs in the UI, making it look like an OEM key.
When the keys reach their maximum activation limit or Microsoft blocks them, this will become useless, unless Nabalum has an unlimited supply of MSDN keys.
Back up your tokens.dat file if you must have a version other than Ultimate..
FAQ:
Q: I the novice user of the PC, saw that there are various activators Windows 7 Loader. What of them to select?
A: To beginners and those who not ready to restore the loader, owing to impossibility to boot after application of activators, it is recommended to use only safe Windows 7 Loader extreme Edition v3. If the "Loader" method used then press "Cancel" button after reboot.
Q: How to use the activator?
A: Start w7lxe.exe, do nothing, wait when all makes the activator in an automatic mode.
Q: Online genuine validation shows the error.
A: KB971033 is blocked for the purpose of preventing possible activation loss in the future.
Q: Can't Microsoft begin to ban modified BIOS with SLIC 2.x?
A: Yes, it is theoretically possible. In Windows Vista times loaders banning was just theory too.
Q: What emulation mode is used by default?
A: Safest emulation is used for SLIC emulator check. If SLIC emulation and activation has passed successfully than UnSafe emulation.
Q: For me it was not initial the load menu and delay time for boot menu but why after application of the "Loader" method there is 30 second return counting?
A: Such occurs only at the first reboot what in case if the SLIC emulator does not work (black screen) it was possible to reboot and use the native choice Windows 7. Other activators, in the case if the SLIC emulator does notwork, it demands to restore procedure with installation DVD usage.
Q: I do not wish to use illegal keys and KMS servers, but thus I wish to have to have "genuine software" status. What can recommend?
A: Use the grace period. For limitation overcoming on the maximum period ofusage (4x30=120 days) to apply the "Trial Reset" method to reset of counters:
w7lxe.exe->Trial Reset->Activate
or
w7lxe.exe /method=TrialReset
Q: How to restore system after unsuccessful usage of TrialReset method by 3..115-3.118 version?
A: Run
w7lxe.exe /trial-recovery
from different windows 7 or Windows Vista installation.
Q: I wish to make on Windows 7 and Windows Vista 49516 grace days the "49516 Trial Days" method as a constant working solution of a question about activation.
A: It is not necessary to make such choice as a constant basis. With the advent of the "Trial Reset" method the such solution has lost sense. Though for Windows Server 2008R2/2008 it is quite applicable. The "49516 Trial Days" method now has more likely fact-finding character that such is possible.
Q: After application of the "Loader" method activation does not occur. Whatto do?
A:
1) Advanced Mode->Boot Loader->Install
2) Reboot
3) Advanced Mode->Upload Screenshot
Or keyboard->PrintScreen; Run->MsPaint->Paste->Save; http://imageshack.us/->Browse...->start upload
4) Ask advanced users for help, having placed a screenshot.
Q: Used the "Loader" method, after rebooting the activator choice (Windows 7 Loader XE) does not load Windows. It was necessary to take advantage of the original choice.
A: It most likely means that the SLIC emulator used by default does not work on the given computer.
Try other emulators (it is necessary to reboot each time):
Advanced Mode->Boot Loader: MBR SLIC Loader->Install
Advanced Mode->Boot Loader: Vista Boot 08.0501->Install
Advanced Mode->Boot Loader: Vista Loader 2.1.2->Install
Advanced Mode->Boot Loader: WOW7 Loader->Install
Advanced Mode->Boot Loader: W7 Loader (Default)->Install
Advanced Mode->Boot Loader: W7 Loader (Alternative)->Install
Advanced Mode->Boot Loader: W7 Loader (LowMemory)->Install
Advanced Mode->Boot Loader: SLIC Driver->Install
Q: How to change delay time for boot menu?
A: Advanced Mode->Boot Loader->timeouts
Q: In what advantage Safest emulation?
A: Always there is a possibility after rebooting to load Windows that is important when the SLIC emulator does not work. Safe emulation should gives the such possibility too.
Q: At start the activator shows the message that it supports only FAT and NTFS file systems.
A: It is possible to skip compulsorily the check of the file system and to start the activator:
w7lxe.exe/fscheck=off
Or for preventing from undesirable effects:
w7lxe.exe/fscheck=off/bootsect=off /mbr=off
- In these two variants UnSafe emulation does not work.
Q: In the list of warnings it is written: "Loader: SCSI boot device detected!". What consequences can occur owing to application of the "Loader" method?
A: Warnings specify in the reason there can not pass activation. In this case SLIC emulation will probably not work.
If the emulator has not worked, in such situation it is necessary to try:
Advanced Mode->Boot Loader: Vista Boot 08.0501->Install
Advanced Mode->Boot Loader: SLIC Driver->Install
Q: In the list of warnings it is written: "Incomplite SLIC(OEMX) detected!"..
A: It is necessary to try:
Advanced Mode->Boot Loader: MBR SLIC Loader->Install
Q: How the automatic mode of the activator works? How it makes a choice of a method for the recommendation?
A: If for the installed edition Windows exists OEM:SLP key and SLIC is detected - the "Certificate" method is recommended.
If SLIC is absent - the "Loader" method.
If for the installed edition of Windows does not exist OEM:SLP key - the "180+ Days" method.
Thus all line of editions Windows 7/Vista/2008R2/2008 becomes covered (Except N and E editions which can be activated by self-decision). if Windows marked as "Pirated" Or other methods are not applicable - than "Trial Reset" method.
Q: What sequence of operations corresponds to the "Loader" method in the automatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: OEM:SLP (OEM) Key->Install
2) Advanced Mode->Key AND Certificates->Certificate->Install
3) Advanced Mode->Boot Loader->Install
4) Reboot
If SLIC emulation and activation has passed successfully:
5) Advanced Mode->Boot Loader->Emulation: UnSafe->Install
6) Reboot
Q: What sequence of operations corresponds to the "180+ Days" method in theautomatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: Volume:GVLK (Volume) Key->Install
2) Advanced Mode->KMS Activation->Activate
Q: What sequence of operations corresponds to the "Certificate" method in the automatic mode?
A:
1) Advanced Mode->Key AND Certificates->Key: OEM:SLP (OEM) Key->Install
2) Advanced Mode->Key AND Certificates->Certificate->Install
Q: I has bought a new computer how to extract all information linked to activation?
A:
1) Advanced Mode->Windows->Dump (Certificate) - keeps the certificate
2) Advanced Mode->BIOS->Dump (SLIC) - saves SLIC
3) Product Key Info->Product Key - shows the installed key
Q: How to return the Windows 7 boot screen and the hibernation mode if 3.011-3.014 version has been used?
A:
1) w7lxe.exe->Loader->Deactivate
2) Reboot
3) w7lxe.exe->Loader->Activate
Q: Activated, but activation is lost each time after hibernation.
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
or
bcdedit -store \boot\lxe ...
Q: For me it is installed Windows XP and Windows 7. After activation there was a third choice "Windows 7 Loader XE". Whether it is possible to delete the native choice Windows 7?
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
Or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
- the such solution is preferable.
Q: It is necessary to customize loading Windows through bcdedit, in particular bcdedit-set testsigning on and HASP driver does not work.
A: Advanced Mode->Boot Loader->Emulation: Safe->Install
Or
Advanced Mode->Boot Loader->Emulation: UnSafe->Install
Q: At loading computer there is a flashing menu. How to remove the flashingor the menu?
A: Advanced Mode->Boot Loader->Emulation: UnSafe->Install
Q: I wish to activate at once through UnSafe emulation. Whether it is necessary so to do?
A: No, it is recommended to pick up in the beginning the working SLIC emulator, with which Windows is activated.
After that it is possible to install through UnSafe SLIC emulation, with the big share of probability, it will work without complications.
Q: I use... (Something like a virtual file system) for disk image creation in real time. It boots before Windows - I am afraid to use the "Loader" method.
A: In an automatic mode (Safest emulation) usually the boot sector and the boot loader are not rewritten.
What to prevent those exclusive situations in which the activator all the same rewrites boot sector, it is possible to use the command line key:
w7lxe.exe/bootsect=off /mbr=off
Q: What physical changes bring in system for UnSafe, Safe and Safest emulation modes?
A:
Safest - changes mention only the boot menu.
Safe - changes mention only the boot loader.
UnSafe - changes mention boot sector and the loader.
Q: What changes bring in process of loading Windows for UnSafe, Safe and Safest emulation modes?
A:
Safest - the activator loader calls Windows.
Safe - the activator loader calls the original boot loader.
UnSafe - the boot sector calls the activator loader, the activator loader calls the original boot loader.
Q: In what emulation mode (UnSafe, Safe, Safest) other activators Windows 7Loader work?
A: UnSafe
Q: I have a legal MSDN key for edition distinct from that which is installed, Windows refuses to accept it.
A: Advanced Mode->Key AND Certificates->Key: Retail (MSDN) Key->Install
Q: How the activator allows installing keys of editions distinct from that which has been installed?
A: Such it is possible thanks to existence of the internal mechanism Windows "Anytime Upgrade". Direct interaction of the activator with it allows notbreaking functioning of the activation mechanism (in difference of other "universal" activators).
Q: How to get the information about the new key?
A: Advanced Mode->Key AND Certificate->Key->Get Info
Q: Where to learn what keys of the command line and external files support the activator?
A: Advanced Mode->Windows 7 Loader XE->Info
Q: Where to learn the detailed information about Safest, Safe, Unsafe emulation?
A: The scheme in archive: Info\w7lxe-emu1-3300.png
//
SLIC what it is how it works overview
Just some shamelessly stolen cut and pasted basic overview info for so many newbies like myself learning just what SLIC is and how it works. This first part covers SLP 1.0.
We are all fairly much aware of how SLP 2.0 works under Vista: The BIOSof an OEM computer has a special ACPI Table called a Software Licencing (SLIC) table which identifies the machine, a special certificate is installedon the computer which validates the SLIC table and authorizes the installation, and a Royalty OEM serial key is used to identify the version of Windows installed. When all three components are installed, the system self-activates.
Under Windows XP, SLP also exists, but in an earlier version (SLP 1.0).this system works similarly to the version used by Vista in that it uses aBIOS component to identify the machine as an OEM manufactured one, a groupof files to validate the BIOS and authorize the installation, and a serialkey to allow the installation of the desired OS.
However, the similarity between SLP 1.0 and SLP 2.0 ends there.
One of the biggest differences is that the BIOS component of SLP 1.0 isnot a SLIC table. Instead, it is a simple text string stored at some specifc location within the BIOS DMI data area. No encryption or fancy algorithyms are used to hide this string. However, some OEM machines do go a step further and calculate checksums on multiple blocks within the BIOS to identify the machine.
While the BIOS component is much simpler under SLP 1.0, the opposite istrue of the validation file. Instead of using a certificate which is compared through an encryption algorithm to the BIOS component, the SLP used by XP requires a series of four files containing an active scanning and validation program that is used to authenticate the installation. These files allhave the name OEMBIOS but a different extension and can be found within the i386 folder of the XP installer CD. (The files are installed to the Windows\System32 folder of the XP installation, as well.)
As for the installation key, all SLP 1.0 keys are manufacturer specific.. A Dell OEM installation cannot use an Acer CD key, for example. This is different from SLP 2..0 where the Installation keys are common to all manufacturers.
A program such as an emulator to make XP think it is an OEM machine is not possible under SLP 1.0, as the validation routine actually scans the existing BIOS ROM chip.
While an emulator cannot be had, modifying the system to use SLP 1.0 isvery simplistic. A common program called a DMI Editor will allow you to modify the DMI configuration data to insert the required string into a non-OEM board. On most OEM systems, this is nothing more than the name of the manufacturer embedded in the DMI data as the System Manufacturer.
(Some OEM machines use further validation, requiring that multiple blocks of memory in the BIOS chip match what the original machine's BIOS contained. Since this would require severe modification to the BIOS program code to achieve, most people simply ignore these OEM brands altogether.)
What string you must insert depends on what OEMBIOS.* files you have onyour installation CD. Several sites have are around which both host the OEMBIOS files and provide the specific details of the correct manufacturer's string and how to edit it. Using those OEMBIOS files, you can easily modifya regular XP home or Pro CD into an OEM one - merely by copying the files over and embedding the correct serial key.
and from MS....
System Locked Preinstallation, often abbreviated as SLP, is a procedureused by major OEM computer manufacturers in order to preactivate Microsoft's operating systems Windows XP, Windows Server 2003 and Windows Vista before mass distribution. Operating systems that use SLP check for a particulartext string in a computer's BIOS upon booting. If the text string does notmatch the information stored in the particular installation's OEMBIOS files, the user is prompted to activate his or her copy as normal. This effectively "locks" the operating system to the qualified motherboard. In addition, if an end user feels the need to perform a "clean install" of Windows, and if the manufacturer supplies the user with an installation disc (not a "System Recovery" disc that is a hard drive image), the user will not be prompted to activate the copy, given that the installation is performed on the same motherboard. Furthermore, because the check only involves the BIOS andnot hardware, a user is allowed to change virtually all hardware components within the machine, a procedure that would normally trigger re-activationin retail XP/Server 2003 copies.
It is important to note that SLP installations still require a product key, which are unique to the specific version of Windows (Home, Professional, Server, etc...). The product key printed on the Certificate of Authenticity affixed to an OEM assembled computer will usually suffice. As of February 28, 2005[1], those keys were invalidated for normal activation by Microsoft in an effort to further reduce software piracy, but does not apply to SLP. If the COA product key is lost, then product key finders, readily available on the Internet, can decrypt the key from a local installation. Keys from either source will allow the user to avoid activation upon reinstallation. Also, Microsoft released the following generic product keys that can beused to avoid product activation on any SLP-enabled computer using the corresponding version of Windows XP:
(Please note that the following keys are not volume license keys. The installation source must also be SLP-enabled by the manufacturer.)
Windows XP Professional (32-bit)
Windows XP Professional (64-bit)
Windows XP Tablet PC Edition
UP-gen [PUP] 20121002
