The timebomb - what really happens

I searched around trying to find out what would happen when the timebomb (beta expiry) comes around. It seems like no one had tried it! So I decided to boot into a Linux live cd and change my date/time to find out (my bios has no option of changing date/time). I tried the method for both, an activated copy and an unactivated copy. The unactivated copy had the wallpaper go black, and the "This copy of Windows is not genuine" watermark appeared (I was still in the 30 grace period before). The activated copy done exactly the same (as well as System Properties not showing the genuine label anymore). I speculated that it may go into the RFM that was with Vista pre-SP1, but it didn't, Windows just became not genuine.

Hi, Termana,Thanks for sharing that ,well done.

This test doesn't work properly since there are all sorts of "Time checks" on the Internet that can check the REAL date / time.

The ONLY way to check this (and I'm sure I posted this on the Forum somewhere -- ages ago however) is to do the following.

(Image your system first so you can restore it again afterwards. )

1) Ensure your computer is DISCONNECTED FROM THE INTERNET AND YOUR ROUTER completely. It has to be a 100% stand alone machine.

2) set the BIOS date and time to say 3 periods ( 3 different tests required ). Boot up each time DISCONNECTED from any Network, or Router.

a) say 1 or 2 days before expiry.
b) just after expiry
c) say 30 days AFTER expiry.

Boot up and check what Windows does.

You'll find out very quickly that it DOES expire on the date in Winver and you'll get reduced functionality at step 2 c).

You MUST use the BIOS date (not Windows system date after boot) and keep the machine isolated from any possible date / time "contamination" via Internet - or your Router - which also has a date / time set by the ISP in it.

Windows 7 has all sorts of "Phoning Home" mechanisms in it so whatever date you set via "System date" this will be checked and overridden if necessary as soon as you connect to the Internet.

This is why the test must be done with the computer isolated from any Network and the date / time set from the BIOS BEFORE WINDOWS IS BOOTED.

Even this in future might not be possible any more as newer BIOS chips could possibly make use of the "International Atomic Clock Radio signal". You'd only then be able to set the Local timezone variation.

AFAIK the BIOS hasn't yet implemented the "International Atomic Clock" feature but it could -- would save the need for a battery in the BIOS and possibly even the RTC (Real time Clock) function as a separate chip.

Cheers
jimbo

Interesting.

The computer was disconnected from a network at all times during testing, and I used a Linux live cd to change my machines date/time.

Good man, well done.

Termana said:

The computer was disconnected from a network at all times during testing, and I used a Linux live cd to change my machines date/time.

Yes but if you then did connect to the internet it may check.

For example if you have a genuine copy of xp, set your date and time wrong then run the genuine test, it will fail as it checks the date.

Well will someone make a program that blocks windows seven from connecting to the internet to check it the time is correct. I know that they have a time server and it checks with that but if someone would make a program that would make it block the connection between windows seven and the time server it wouldn't expire as long as you keep the time on your system back like a year!

mjgaming said:

Well will someone make a program that blocks windows seven from connecting to the internet to check it the time is correct. I know that they have a time server and it checks with that but if someone would make a program that would make it block the connection between windows seven and the time server it wouldn't expire as long as you keep the time on your system back like a year!

Anyone with a laptop can probably just disable their NIC to cut the connection.

just pull the ethernet plug to your router/adsl/cable modem LOL