Wednesday, January 19, 2011

Windows Loader v1.9.5

email post
Windows Loader v1.9.5
The safest and easiest way to activate your Windows.

About

This is the loader application thats used by millions of people worldwide, well known for passing Microsoft's WAT (Windows Activation Technologies) and is arguably the safest Windows activation exploit ever created. The application itself injects a SLIC (System Licensed Internal Code) into your system before Windows boots, this is what fools Windows into thinking it's genuine.


Features

Can be run as a standalone application
Works well with all system languages
Argument support for silent installs
Can be used for pre-activation
Application integrity checking
Custom error handling
Support for hidden partitions and complex setups
Can work alongside Linux's GRUB or any other boot manager
Works with TrueCrypt and many other types of hard drive encryption applications
Add your own certificates and serials externally
Offers certificate and serial installation only for users with an existing SLIC 2.1
Automated system profiling (The application matches everything up for you)


The rundown

Compatible with all Windows updates ✔ check
This will run on x86 and x64 systems ✔ check
This can activate all Windows versions at the same time, just install it on each ✔ check
No core system files get modified ✔ check
No extra processes are run so you have nothing eating at your RAM ✔ check
All key parts of the exploit are encrypted with a custom encryption ✔ check
The exploit runs before Windows so it's harder for Microsoft to prevent ✔ check
The exploit patches all necessary tables making activation look authentic ✔ check
The application will select the best profile for your system during installation ✔ check
Each and every user has a unique version of the exploit installed on his/her system ✔ check

    Supported operating systems:
  • Windows 7 Ultimate
  • Windows 7 Professional
  • Windows 7 Home Premium
  • Windows 7 Home Basic
  • Windows 7 Starter
  • Windows Vista Ultimate
  • Windows Vista Business
  • Windows Vista Business N
  • Windows Vista Home Premium
  • Windows Vista Home Basic
  • Windows Vista Home Basic N
  • Windows Vista Starter
  • Windows Server 2008 R2: Enterprise
  • Windows Server 2008 R2: Standard
  • Windows Server 2008 R2: Foundation
  • Windows Server 2008: Enterprise
  • Windows Server 2008: Standard
  • Windows Server 2008: Foundation
  • Windows Small Business Server 2008

Note: You must be running build 7600 or greater for Windows 7 and Windows Server 2008 R2.
Note: Windows 7 N and E editions will only be supported when OEM SLP serials leak for them editions.


Application integrity checking?

Hover your mouse over the green, amber or red icon to see detailed application information.

Note: Even if the icon is green someone might have found a way around the protection system so it's worth checking that the applications path is always the same as the location from which you launched the application. You should also check that the MD5 matches the MD5 found online.

Download:

Monday, January 17, 2011

How to do with a blue screen?

email post
Blue screen (System crush) is error that may be more common in the Windows system, a mistake. But for most of us, the occurrence may be at his wits end after a blue screen.
Here are some blue screen errors occur when some of the ways. Many ways, but today this part describes how to use Windows De
bugging Tool, or call Windbg, combined with Microsoft's forum to deal with the problem.
 

First, use the blue screen problem WinDBG treatment, to ensure that the system has generated a memory dump file. 

Confirmed the existence of a memory dump file 


The default configuration of Windows 7, the resulting core dump file may be (Kernal Memory Dump) or a small memory dump file (Minidump). If the core dump file, the default will be saved as C: \ Windows \ Memory.dmp, if it is a small memory dump files, relevant documents will be saved in C: \ Windows \ MiniDump directory. 


Therefore, a blue screen, please check the system has no C: \ Windows \ Memory.dmp this file, or C: \ Windows \ MiniDump directory file named by date. For example, Mini010810-01.dmp is January 8, 2010 the first small memory dump file.
If you do not have the memory dump file, please refer to the relevant documentation. 


Install Windows Debugging Tool (WinDBG)
Next, we want to install Windbg the. WinDBG can download the Microsoft 32-bit address is: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

, 64-bit address is:
http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx


 Note WinDBG only in English. You just find a place to both download and install the latest version of it. If you do not really understand English, you download directly to these two addresses: 32:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi

, 64 bit:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi
http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi


Next all the way to safety and then turn on it. An WinDBG transfer file size, probably around 15-30 trillion. 

Configuring Windows Debugging Tool (WinDBG)
Analysis of the memory dump file by WinDBG, we want to configure what WinDBG.
First, choose a temporary directory stored Symbol files. For example, create a directory called C: \ Temp
Then, open WinDBG, in the File Menu - "choose Symbol File Path. In the Open dialog box, enter:
SRV * c: \ temp * http://msdl.microsoft.com/download/symbols
Select OK OK. WinDBG to configured.
With the Windows Debugging Tool (WinDBG) of memory dump file
In WinDBG which, in the File menu, select Open Crash Dump, and then find that in front of said core memory dump file or a small memory dump file, select Open. Wait a moment, if you need to download from the Microsoft Web site Symbole documents, the time may be rather long. If not a large number of Warning, it means setup is successful. If Your debugger is not using the correct symbols like the information on configuration issues, to carefully check the previous step.
Wait until there Use! Analyze-v to get detailed debugging information. Words and 0: kd> prompt.
Follow the prompts, enter! Analyze-v command. Wait for command to complete.
Analysis of Windows Debugging Tool (WinDBG) results