New
#11
Thanx so much for that valuable input. I struggled to revive a laptop for 3 harrowing days. With your inputs, it is solved now
Great advice
I didn't have the prob yet and this thread should be a sticky one...it might be lost in the forum!:)
This is an excellent tip. I was able to find NOTHING that helped my issue. For me, it started out that I was dual-booting XP & Windows 7-64. I wasn't able to mark my 7 partition as primary and active, and after much frustration erased the XP partition.
Yadda yadda, it all became unusable. I backed up my Win7 partition with GSS and couldn't get it working thanks to this problem detailed by the OP. After using his trick (and I had tried EVERYTHING else), it all works fine now.
All this just to get rid of XP, and now I'm almost wishing I hadn't given the problems I started having...
Thank you OP, I have been messing with this for an entire week, performing roughly 6 restores on my RAID array. I knew it would be something easy, but could never find the answer. If this thread is not a sticky, please make it so!
Hey guys. I have had this exact problem show up ever since the AVG debacle with Dec1 update. I followed the links I found here to get my laptop up and running again and now I get the "Windows 7, build 7600, This Copy of Windows is not Genuine" message. I have an ASUS UL50v laptop that is only like six months old I think.
I'm not sure where to start looking. Is this fix a good place to start? Thanks
This fix was only used after restoring from a Norton Ghost backup. It is a last resort to avoid a clean install. If you haven't recently done a restore I would try this first>
Free Antivirus | Forum - Fix For Update/Boot Error Vista
If you did get to this point from restoring via backup software it should work for you.
I had seen this thread previiously but a new problem I'm having triggered a thought: could this be related???
I have a lab mule machine, a little Aopen mini-cube that has a legit copy of Windows 7 Home Premium. Originally as I acquired it, the load was on a 20GB drive. I imaged the system using Paragon B&R Free, and "voila'" moved it over to a 80GB 7200rpm drive. Came up flawlessly, activated and validated and sanctified. No problemo....
Then I got fancy, wanting to lower power consumption and heat buildup since the 80 was a fullsize drive: I bought a 7200rpm 100GB NOTEBOOK drive - Did the same thing again, using Paragon to image the now-80GB copy, restoring it to the 100GB, process-wise just like previous. This time I get the black screen with "THIS COPY OF WINDOWS IS NOT GENUINE".
I was in a hurry at the time, so the short path was to just drop the green idea and return to the 80GB brick. I assumed that the issue was non-Activation due to the hardware change lever being tripped. But maybe not.
Can someone smarter than me tell me which issue I encountered?
Last edited by zapp22; 09 Dec 2010 at 09:01. Reason: mistake