HI all. I installed win 7 on my sony vaio laptop 2 weeks ago and i used 7loader 1.5. I installed that update without knowing a few days ago and nothing happened. Windows is still activated. Should I be worried?
First post... I want to thank you all for the info shared here and share my experience with WAT. Updated an Asus board (w7 x64) without any problem but my second pc, a shuttle kpc (w7 x86), ended up flagged as not genuine. Both with slic modded bios using the tools found here. Didnt know why the 2nd pc was flagged, so I decided to format and reinstall. This time it didn't presented any problem, it updated just fine. My guess, WAT is faulty and may flag a pc with "genuine" slic cert and key. Ended up restoring a backup and hiding the update on my shuttle. hope this help someone. and again thanks all for the great info found on this board.
Most people from the Netherlands (myself included) still haven't received the KB971033 update via WU (as of February 28th 01:32AM). Eventually, it will/should arrive here also via the Windows Update service. So nothing is wrong as far as I can tell
It seems that, at this stage, if you have the update you have enabled M$ to catalog your machine, bios ,OS,and activation method. The general consensus seems to be that bios mods will be the last to go, but it's only a matter of time before M$ puts subtle squeezes to the next easiest activators, until they are squeezing legit machines. Probably best to uninstall update,or reinstall OS and don't install update. There are plenty of experimenters here, so stay tuned, for a clearer understanding of what WAT might do next, and the gurus replies down the road.
Checks on BIOS 'ses dates will (i.m.ho.) NOT work for M$. I own a legitimate Windows 7 upgrade which *could* have been installed (in fact its is now installed nowhere) on machines with BIOS'ses from 2004 I own myself. Such a machine then certainly could be running a legitimate copy of Windows (my machines are certainly *capable* of running Windows 7 ). Like probably many others, I would be very angry if my machine would be diabled from running Windows 7 just becasue of the date of its BIOS.
Yes, but in case of an Upgrade install, the key would show up as Retail in MS's data and not OEM-SLP.
It's a boxed upgrade, no? The thought is MS could use BIOS dates for OEM:SLP genuine check only NOT for retail or OEM:system builder, or upgrade, or KMS/MAK volume licence. Why is that so hard for people to understand? It's highly unlikely an OEM:SLP machine would have a BIOS dated before 2009. But that has no impact on other licencing methods.
beats me why everyone is looking at complicated workarrounds to WAT. I loaded it, and ran it so my computer shows its installed. That way I am sweet for updates and even SP1. BUT you can totally manipulate it easily this way. This includes changing the phone home period from 90 days to 9000 days if you wish For people who don't want WAT to run every 90 days, you can disable the scheduled task. •Run "taskschd.msc". •Goto Task Scheduler Library -> Microsoft -> Windows -> Windows Activation Technologies. •Double-click on ValidationTask, goto Triggers Tab and click on edit and uncheck Enabled. •Repeat the above step for ValidationTaskDeadline it now wont phone home, BUT is still installed If you want to change the 90 days, well same area, BUT change 90 days to whatever period you like.
You can also disable it at command line: Code: schtasks /change /disable /tn "\Microsoft\Windows\Windows Activation Technologies\ValidationTask" && schtasks /change /disable /tn "\Microsoft\Windows\Windows Activation Technologies\ValidationTaskDeadline"
I've upgraded three laptops to SLIC BIOS versions and they work fine. On two of the three I reformatted and loaded from an RTM version. On the third I just changed the key and installed the certificate. On one of the 3 laptops I did originally use a loader (before I discovered BIOS mods) but can't now remember which machine it was on. Obviously if it was one of the two I reloaded from scratch that's fine. Is there any way to tell if a loader is in place on the third one?
If it was Daz's loader, Look for a hidden system file of around 300kb and exactly 5 UpperCase characters in length in the root of the C:\ drive. (ie: C:\BSHIA in mine at 302Kb) Not sure how to easily tell, other than maybe try 'everest' and look for an emulated slic, which many loaders will still fool anyway.l