ahashash
asked on
windows date change messed up OS?
i made a winform application vs2010 vb.net, and it has this function where if a certain date comes it should fire an event, the problem:
in order for me to test it, since i cant wait for a future date to come just to see if a msgBox will pop, so i changed the date on the machine from control panel, to be like 3 or 5 or max 6 months ahead, it was 1st dec 2014, i made it june 2015, after i tested it it worked, but when i set the date back to normal i start to get this annoying windows genuine authentication thing, and my copy is not original! it asks me to go online to verify, and i did, but it keeps telling me to buy a copy of windows!!!!!!!!!!!!!! and still pops the messages!!!!!!!!!!
i bought the dell desktop xps ($1300) windows 7, like a year ago, everything is original, nothing on this PC is illegal, so any ideas ????
WINDOWS-AUTH.jpg
in order for me to test it, since i cant wait for a future date to come just to see if a msgBox will pop, so i changed the date on the machine from control panel, to be like 3 or 5 or max 6 months ahead, it was 1st dec 2014, i made it june 2015, after i tested it it worked, but when i set the date back to normal i start to get this annoying windows genuine authentication thing, and my copy is not original! it asks me to go online to verify, and i did, but it keeps telling me to buy a copy of windows!!!!!!!!!!!!!! and still pops the messages!!!!!!!!!!
i bought the dell desktop xps ($1300) windows 7, like a year ago, everything is original, nothing on this PC is illegal, so any ideas ????
WINDOWS-AUTH.jpg
AndyAinscow
Get in touch with Microsoft by phone and explain what has happened. They might be able to help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
1. Are you still running Windows 7 (original version) or have upgraded it to a different version? If yes which one?.
2. Have you tried a System Restore (Start >Search> System Restore) and then see if that works?
3. Open an Admin Command Prompt (Start >Type CMD, right click and Run as Admin) and then type the command SFC /Scannow, wait for a while for it to finish and reboot. If it doesnt work then open same CMD prompt as admin and type slmgr /rearm and restart the system and repeat process with slmgr /ato and see if that works.
1. Are you still running Windows 7 (original version) or have upgraded it to a different version? If yes which one?.
2. Have you tried a System Restore (Start >Search> System Restore) and then see if that works?
3. Open an Admin Command Prompt (Start >Type CMD, right click and Run as Admin) and then type the command SFC /Scannow, wait for a while for it to finish and reboot. If it doesnt work then open same CMD prompt as admin and type slmgr /rearm and restart the system and repeat process with slmgr /ato and see if that works.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@ahashash
@MASQ
Check complete comment writer here:
http://www.makeuseof.com/t
Thank you MASQ.
@MASQ
Check complete comment writer here:
http://www.makeuseof.com/t
Thank you MASQ.
In the future when testing, configuring your time frame to 20 minutes from now, and then waiting for the event would have achieved the same result:
1) confirm that your logic works
2) and see the event you planned for since it makes little difference when testing.
1) confirm that your logic works
2) and see the event you planned for since it makes little difference when testing.
>>In the future when testing, configuring your time frame to 20 minutes from now, and then waiting for the event would have achieved the same result:
Where do you see that in the question (eg. If the date the event should fire on is the first of april) ?
Where do you see that in the question (eg. If the date the event should fire on is the first of april) ?
Andy,
You and others experts addressed how to remedy the situation the asker has wound up.
My comment deals with avoiding situations where one has to set their system to a date in the future in order to test an application's behavior when the set time is arrived or passed.
i.e. if I write an application that needs to trigger an event when 182 days lapse from a specific event. A test to see that the mechanics work as designed would be enough to use a 30 seconds, a 2 minutes, even an hour to validate as long (I, as the programmer would account for the condition adjustment).
You and others experts addressed how to remedy the situation the asker has wound up.
My comment deals with avoiding situations where one has to set their system to a date in the future in order to test an application's behavior when the set time is arrived or passed.
i.e. if I write an application that needs to trigger an event when 182 days lapse from a specific event. A test to see that the mechanics work as designed would be enough to use a 30 seconds, a 2 minutes, even an hour to validate as long (I, as the programmer would account for the condition adjustment).
I agree there would be 'better' ways to test this than doing what was done - but for a beginner just adding minutes instead of months might still leave them uncertain if it really was correct.
Running inside a virtual machine could be another that would test the real code.
Unfortunately this method to test was used and I hope the asker of the question has learnt something from it.
Running inside a virtual machine could be another that would test the real code.
Unfortunately this method to test was used and I hope the asker of the question has learnt something from it.
ASKER
Worked like a charm..........many many many thanx to all