Windows Loader v1.8.9-DAZ
Here we have new version of well known Windows activator-loader by DAZ. You can read changelog here. Few tweaks and fixes have been added in this version.

Release Name: Windows.Loader.v1.8.9-DAZ
Size: 6 MB
Links: Nfo, Homepage
Download: Hotfile, Torrent Search

Comments (43)
LETITBIT.NET
http://letitbit.net/download/79410.790acd683cac343b19db7874bd41aec0a/w.l.1.8.9.rar.html
what will do this application? thanks
@ xD
This will activate you Windows OS. duhhhhh…..
whats the point of all these new versions
back when windows 7 got released in about a week “Windows 7 Loader by Orbit30 And Hazar” appeared i used it then and my windows is still activated with latest updates.
this loader is completely unnecessary
@ sssss
Did you try to read changelog??? Did you???
You don’t know anything…. This is the best activator!
This guy must enjoy seeing his name on every torrent site
“Hey guys, here’s my new version. I changed one bit and increment the build number by 1, weeeeeeeeeeeeee!”
STOP the madness, this will never pass SP1…
@ sssss
Read the read me file more often.
@ Beast
You don’t understand how the loader works, nor what SLIC injetion is. This will remain working always and it already passes the SP1 beta builds.
@ Others
Wait for version 1.9, this version has a booting issue on some systems. Will be fixed this weekend.
Release Name: Windows.Loader.v1.8.9-DAZ
High Speed Link
No Wait Times
No Password
direct download link for Windows 7 Loader v1.8.9 by Daz
http://www.freedownloadex.com/windows-7-loader-1-8-9-p275.html
Windows 7 activator & loader collection
by DAZ / Hazar / Orbit30 / others
latest versions
► http://uploading.com/files/d7abe13e/win-7-loader-activator-collection-seven.rar/
Simple instructions included.
One of these activators will definitely work for You!
Enjoy!
Rapidly Fresh!
► http://uploading.com/files/d138db85/Windows.Loader.v1.8.9-DAZ.rar
Enjoy!
@Daz: Yes, I know how SLIC injection works and exactly that is the problem: INJECTION. It is introduced into RAM using a modified GRUB loader. Therefore, Microsoft can scan for the loader (always in the root of the active partition) and analyze it just like it does malware using it’s Windows Defender/Forefront products, etc.
The fact that it passes SP1 betas means SQUAT. Do you really think Microsoft will introduce counter-piracy measures in a Beta so every geek out there can work on countermeasures before RTM? Come on, you’re smarter than that, no?
I used to use your loader, but once I upgraded to one of your newer version, it quit working. So I learned how to SLP-MOD my BIOSes and never went back. Also, although possible, BIOS mods are hard to detect if done right. Your loader not so much, it sits right there, in plain view, for everybody to disassemble and scan.
You coming here to comment about your own release only reinforces my view of you: you like to stroke your own ego.
Windows.Loader.v1.8.9-DAZ
http://uploading.com/files/3b4253fb/Windows.Loader.v1.8.9-DAZ.rar
Thanks Daz… Really appreciate the superb work you do for us all
You are the man!
@ Beast
Wrong, it doesn’t go into RAM and you clearly have very little understanding.
When a BIOS loads it copies it’s tables to memory, all the loader does it modify these tables in memory (EBDA/ACPI) and make them look like OEM. This means that there is absolutely no way that Windows can tell the difference between the two.
Now note number 2. The loader is not always installed onto the active partition and even when it is nothing can prove it’s an exploit because each users file is different. Different hash, different data, simply different. That not enough for you? Then have you stopped to think what happens when the loader is installed to a Linux or Mac partition that Windows and all file scanner applications can’t even read?
The only thing integrated into SP1 is the WAT update and the loader already passes that. To Windows the loader is just a file that happens to be on the HDD, it’s not actually run within Windows and as I said originally Windows can’t tell that the ACPI tables have been modified.
The reason I visited a few sites with regards to 1.8.9 is because it has a bug that causes a hang on a few systems. You sir have now been schooled.
Daz changes his loader version more times than he changes his undies…
Actually he releases a new version once every 1-2 weeks which is just about right. Think about it, the loader has to work on millions of systems and hes always adding in support for more. Can’t hate a guy just cause hes trying to help people.
Uhm, what?
“Wrong, it doesn’t go into RAM” and a few insults later “When a BIOS loads it copies it’s tables to memory, all the loader does it modify these tables in memory”
OK, unless definitions have changed, RAM means “Random Access Memory” so you are basically restating what I was saying. “Windows Loader” modifies data in RAM using a GRUB loader. That loader can be detected the same way a virus is detected because no matter how much morphing you apply to the code, certain sequences and behaviors will always stay the same. And if Microsoft really really wants to, it will detect the loader.
But hey, why do I care right? Loaders are for newbs and we will see who passes SP1 and who doesn’t
Memory = ACPI memory, EBDA memory. Not RAM as you’d call it.
Theres no way Windows can detect it if it makes the tables identical in every way to a retail OEM system, it’s just not possible because once the loader has run it exits leaving no trace to say something modified the tables.
I obviously can’t convince you with words so I won’t waste my time trying to explain it, I will instead let the application do the talking when it passes SP1 and all tests thrown at it come September
Yes, I’m that confident.
Hey Daz, I know this is no support forum, but can you offer any advice why both v1.8.8 and v1.8.9 do not successfully make Microsoft.Windows.7.ULTIMATE.x86.OEM.DVD-BIE genuine on my Acer 6920G?
I uninstalled KB971033 and then (I know now that I should have rebooted before) applied the v1.8.8, after changing the settings from Dell to Acer. Rebooted, it came up as before. Tried again with the v1.8.9 (also changed to Acer), rebooted, no change.
Any ideas? If it’s not the right place to post an answer, just send to eterna111@yahoo.com – thanks!
Hello Christian,
Run “sfc /scannow” from command prompt as an administrator and then install the loader and reboot. Once you’ve done that visit the MS genuine website and everything should pass. If you don’t pass then check that under the details line (within the loader application) that it says “v2.1″, if it doesn’t install the loader again with the legacy option set.
Hope this helps!