Author Topic: Win 7 Pro x64 reporting not genuine after using Windows Repair 2.10.4 (Read 10421 times)

MM · « **on:** January 31, 2015, 11:22:25 am »

Hi, I hate to bring this to your attention (as others already did), I see I'm not the only one ...
There's NO way 4 me to have a non-genuine Windows package. It came along with my brand new, sealed, HP workstation and I have a RECOVERY partition on one of the hdd's for emergency cases.
I was stupid enough to use a utility to "cleanup" the registry. And afterwards, the problems started ...
I used your AIO package, solved most of the issues, except some account ownership problems and Defender not willing to start anymore.
But, by far, the most annoying one is this popup appearing all the time to warn me that my windows is not genuine.
Worst case scenario for me: Backup (A LOT of files!!!) and reinstall everything, but I have the complete Master Collection CS6 from Adobe installed and going again to the whole process of reinstalling gives me the shivers ...
(The attached printscreen has some areas blurred by me for the obvious reason.)
Any ideas?
Thanks in advance
MM

Shane · « **Reply #1 on:** February 02, 2015, 04:32:50 pm »

None of the repairs touch anything to do with activation. Every time someone has reported this to me it had been because their was an activation crack on the system, and that crack had written to the hosts file so that the activation wouldnt talk to the MS servers. Well my Repair Hosts file puts the host file back to defaults.

So lets check and see if that is what happened. My Repair would have renamed the old host files to another name and in the same folder. So go to "C:\Windows\System32\drivers\etc"

And post any extra hosts files in there and lets take a look

Shane

MM · « **Reply #2 on:** February 04, 2015, 11:48:24 am »

Hey Shane,
Thanks for the reply.
Please find attached a printscreen with the content of my etc folder.
Do you mant me to open one of the files and see what's in it?

Thanks in advance
MM

Shane · « **Reply #3 on:** February 05, 2015, 02:07:06 am »

Yes, the 3 host_bak files

Shane

MM · « **Reply #4 on:** February 07, 2015, 04:37:39 pm »

Here we go:
1. hosts_bak_88
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
#   127.0.0.1 localhost
#   ::1 localhost

127.0.0.1 localhost

2. hosts_bak_438
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
#   127.0.0.1 localhost
#   ::1 localhost

127.0.0.1 localhost

3. hosts_bak_230
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
127.0.0.1 localhost
#   ::1 localhost

Shane · « **Reply #5 on:** February 09, 2015, 02:17:24 pm »

Well those all look fine and dont show any blocks to MS at all.

What happens if you go and have windows activate itself?

Shane