Updates today on W 7 and now there is a message showing…….

Topic

New Reply

After the updates today, 17 of them, my computer (W 7 Enterprise) has a little notice at the bottom right corner of the screen “Windows 7, Build 7601, This copy of Windows is not genuine”, which is false. I know the Enterprise systems are not eligible for the automatic update to W 10. My hunch is that MS tried to force a download of W 10 and because this is Enterprise, has now put that notice on my computer. Any ideas from you experts? I’m a self taught intermediate user, no techie here!

Reply | Quote

Replies

Have you tried activating it?

Joe

--Joe

Reply | Quote

I don’t think there’s anything to activate, because MS wouldn’t have put W 10 on my computer. Is that what you mean, activate W 10? Thanks for the thought.

Reply | Quote

No. Activate Win7 Enterprise. You don’t have Win10. You have a problem with what Microsoft sees in the Win7 activation information.

Joe

--Joe

Reply | Quote

I guess I don’t know how to do that, Joe. Bought the computer used with this version of 7 installed, and have just updated it since then. I get the 7 updates, so I thought MS could see that it’s 7. Sorry, I told you I’m no expert! :rolleyes:

Reply | Quote

Go Start – type activate windows – press enter and see what it reports.

Should you need them, these commands run from an elevated command prompt will recreate the licensing store –

net stop sppsvc
(wait until the service has stopped before entering the following lines)

CD %windir%ServiceProfilesNetworkServiceAppDataRoamingMicrosoftSoftwareProtectionPlatform

REN tokens.dat tokens.bar

net start sppsvc

slui.exe

After a couple of seconds the Windows Activation dialog will appear.

You may be asked to re-activate and/or re-enter your product key, or Activation may occur automatically.

If you are asked for your Key, use the one on the COA sticker on the machine’s case, or your current product key if you have upgraded.

Enter shutdown /r /t 00 to effect an immediate reboot and then redo “activate windows” to see what it reports.

Reply | Quote

I can try that tomorrow, Sudo. I’m running out of time today and it’s sounds like I really need to take my time to do that process. BTW, I ran the “magic jelly bean” a while back, to get the key info. Is that the same info you’re talking about? Thank you

Reply | Quote

That depends upon whether Enterprise came pre-installed on the computer and if it is an OEM machine.

MagicJellyBean will list an OEM generic key just as Belarc Advisor will and while being accepted, will render your install as an invalid key when you run activate windows from Start.

If the machine is an OEM build and came with Enterprise then you would use the COA sticker key.

Perhaps you can give us some more info on the pedigree of your machine.

Reply | Quote

That depends upon whether Enterprise came pre-installed on the computer and if it is an OEM machine.

MagicJellyBean will list an OEM generic key just as Belarc Advisor will and while being accepted, will render your install as an invalid key when you run activate windows from Start.

If the machine is an OEM build and came with Enterprise then you would use the COA sticker key.

Perhaps you can give us some more info on the pedigree of your machine.

I’m quite sure the machine was upgraded to 7 before I bought it, not original, and there’s no sticker. I guess I can just live with that “not genuine” note on the screen if it doesn’t cause problems later. I’m totally happy with 7 now and will use it as long as possible. My laptop can upgrade to 10, but I won’t do that till all the problems are solved!

That’s informative to know about the key from Magic Jelly Bean being generic, and Belarc too. Thank you for your time!

Reply | Quote

If it was upgraded to Enterprise then I’m assuming it will not display an OEM key that looks nothing like the normal 25 character key, but Belarc Advisor will be best for that info.

http://www.belarc.com/free_download.html

Reply | Quote

It might be a volume license.

http://www.zdnet.com/article/what-microsoft-wont-tell-you-about-windows-7-licensing/

I think you’re right! I tried the command prompt and it said that it’s not recognized. You’re all very kind to give me these tips. I’ll try Belarc tomorrow; have used it before on another machine. The magic jelly bean key I get is 25 characters, btw. Don’t know yet if that will help with anything. Will try more tomorrow. I’ll see what belarc tells me. Thank you all.

Reply | Quote

The command wasn’t recognized. Just tried copy and paste and it said the same thing. Thanks again.

Reply | Quote

Run the MS Genuine Advantage Diagnostics Tool which will give you similar info, but for me, it still lists the partial generic key as well as the OEM one of which neither correspond to the COA sticker key.

http://go.microsoft.com/fwlink/?linkid=52012

When you click on Copy, it produces a lot more info than what just appears in the screen window output, but you can paste into a Notepad doc and edit it before copy & pasting into the reply box if you want to post its output.

It’s pretty much just the first “paragraph” that is relevant for the forum.

If it is a Volume Licensing key then it would seem to be a bit more involved –

https://msdn.microsoft.com/en-us/library/jj979464(v=winembedded.81).aspx

Reply | Quote

Run the MS Genuine Advantage Diagnostics Tool which will give you similar info, but for me, it still lists the partial generic key as well as the OEM one of which neither correspond to the COA sticker key.

http://go.microsoft.com/fwlink/?linkid=52012

When you click on Copy, it produces a lot more info than what just appears in the screen window output, but you can paste into a Notepad doc and edit it before copy & pasting into the reply box if you want to post its output.

It’s pretty much just the first “paragraph” that is relevant for the forum.

If it is a Volume Licensing key then it would seem to be a bit more involved –

https://msdn.microsoft.com/en-us/library/jj979464(v=winembedded.81).aspx

I’ll try that later. I think I’m getting in over my head!

Reply | Quote

I’ll try that later. I think I’m getting in over my head!

I ran the Tool you referenced. It says “Validation Code: 0”. It shows part of the “product key” and what it shows is the same as the last part of the “CD key” on magic jelly bean. Magic jelly bean also says installed from “volume media”. I think I’m at a dead end and will just have to live with the notice on my screen that Windows is not genuine (b/c it’s “volume” license I guess). I already knew I could not get W 10 on this machine and that’s fine. I don’t want to keep bothering you helpful folks.

Reply | Quote

Interesting. That should be recognized in any version of Windows.

Just to confirm, you are opening the Command Prompt located in the Accessories folder in the Start menu > All Programs…

Yes, that’s what I used.

Reply | Quote

If you want, as you can use the Snipping Tool and attach, just use that for the initial window the Diagnostics Tool produces.

Reply | Quote

It doesn’t say genuine anywhere. I’ve gotten the updates all the time I’ve had the computer, a year or two, so I hope they’ll continue.

Reply | Quote

Unfortunately, I’ve seen this happen before.

Update: I just ended a chat session with a Microsoft Answer Desk tech, and they suggested contacting Volume License Activation at (888) 352 7140.

Thanks so much! I might try that.

Reply | Quote

Can you remember if it said OEM SLP or anything else as to the Windows Licence Type ?

It’s possible that the Software Protection service isn’t running.

To check this, go Start – type services.msc and press enter then scroll down to Software Protection.

It should be showing as Automatic or Automatic (Delayed Start).

While mine shows as Automatic, it doesn’t display it as Started, but you can do that by clicking on it then on Start in the upper left pane.

If it isn’t showing as Auto then right click on it and select Properties and use the dropdown to change its status.

Reply | Quote

Can you remember if it said OEM SLP or anything else as to the Windows Licence Type ?

It’s possible that the Software Protection service isn’t running.

To check this, go Start – type services.msc and press enter then scroll down to Software Protection.

It should be showing as Automatic or Automatic (Delayed Start).

While mine shows as Automatic, it doesn’t display it as Started, but you can do that by clicking on it then on Start in the upper left pane.

If it isn’t showing as Auto then right click on it and select Properties and use the dropdown to change its status.

I changed it from manual to automatic; it said “started”. I’ll have to run that tool again to see about your OEM question, and license type. I’ll also check the link in your last message. Thanks so much!

Reply | Quote

Found this – http://www.microsoft.com/genuine/validate/

See what that makes of it.

Reply | Quote

NonGenuiness can cause some problems down the road. sevenforum.com’s NoelDP and one other person had a couple of suggestions to add to this present pot o’ suggestions.

"Take care of thy backups and thy restores shall take care of thee." Ben Franklin, revisted

Reply | Quote

Sometimes when you change the status of a service to auto, it’s best to reboot so that service will be doing its job at start.

I don’t know if one of the updates was the cause of this as others have reported the not genuine message out of the blue, but if you want to determine if any of the updates was responsible if you still have problems – then you could use your restore points back to before them.

If you still get the not genuine message then post-updates may just have been coincidental or once it flags then it remains as such.

If you no longer get the not genuine message then install just one update at a time until/if it returns – but hopefully what you have done since will resolve without the need to restore.

Reply | Quote

Sometimes when you change the status of a service to auto, it’s best to reboot so that service will be doing its job at start.

I don’t know if one of the updates was the cause of this as others have reported the not genuine message out of the blue, but if you want to determine if any of the updates was responsible if you still have problems – then you could use your restore points back to before them.

If you still get the not genuine message then post-updates may just have been coincidental or once it flags then it remains as such.

If you no longer get the not genuine message then install just one update at a time until/if it returns – but hopefully what you have done since will resolve without the need to restore.

Restore point is an excellent idea and then installing one update at a time. I’m so rattled by this that I didn’t think of that possibility.

Reply | Quote

I assume changing the status of the Software Protection service and a reboot hasn’t resolved anything ?

Did the Validate now link do anything ?

To check the status of your install, go Start – type activate windows and press enter to see what that says.

Did you run the diagnostic tool again to see what the licence type was ?

Reply | Quote

I assume changing the status of the Software Protection service and a reboot hasn’t resolved anything ?

Did the Validate now link do anything ?

To check the status of your install, go Start – type activate windows and press enter to see what that says.

Did you run the diagnostic tool again to see what the licence type was ?

You’re a genius to suggest system restore, thank you! I got rid of the not genuine message. Should have learned my lesson about updates with all the warnings about forced W 10 downloads. I’m sure it was in a W 7 update and I’ll do as you suggested, first read about each one, then go one at a time. The problem must be the volume license, and to try what you suggest above, doesn’t work. Says I don’t have authority, etc., I suppose b/c with volume license i’m not recognized as administrator, though I really am.

So I’m in better shape now getting rid of the not genuine message, and I’ll try some of these other suggestions and maybe call about the volume license. Just don’t want to open a can of worms with MS.

Thank you Sudo and all for so many helpful hints, I really appreciate it. I’ll go slowly now. A HUGE thank you!!

Reply | Quote

Glad to see at least one of the suggestions has worked

If you find the offending update, will you let us know which one it is/was ?

Reply | Quote

Glad to see at least one of the suggestions has worked

If you find the offending update, will you let us know which one it is/was ?

I certainly will. Right after the system restore the whole group of updates, 18! appeared again. Obviously I closed the window and will make a list of them when I have time, and research each one. I’m assuming it was a W7 update and not Malicious Softward Removal Tool or Windows Defender.

Thank you again!!!

Reply | Quote

Now get and write down the product key. If it is a OEM or volume license key it won’t do you much good. But if it is not it may help in the future.

Reply | Quote

Click on each update and then on More info in the right pane, but one to look out for is KB3112343 which is a Telemetry (spy) one.

Reply | Quote

Click on each update and then on More info in the right pane, but one to look out for is KB3112343 which is a Telemetry (spy) one.

3112343 is on the list, but I am having a terrible time! I try to download one update at a time, but the indicator goes on and on and never stops. However they show as downloaded, all of them, after the system restore, but in history of updates they don’t show up. Downloaded, but not removed by system restore? I can’t find out which one is related to W 10, that gave me the not genuine notice.

Reply | Quote

3112343 is on the list, but I am having a terrible time! I try to download one update at a time, but the indicator goes on and on and never stops. However they show as downloaded, all of them, after the system restore, but in history of updates they don’t show up. Downloaded, but not removed by system restore? I can’t find out which one is related to W 10, that gave me the not genuine notice.

Perhaps I should have explained that better.

When you get the notification for updates, click on Important and/or Optional and then uncheck the top box.

This will deselect them all and then click on each and then on More info in the right pane.

Check the box for just one then OK where it will display as just one update to install.

I think KB3112343 relates to updating (aka upgrading).

I also have my update settings set to Check for but let me choose and then you can decide what you want to install from them, but it may just have been a glitch that caused the not genuine error – but updates affect computers in different ways.

Reply | Quote

IMO, “spying” and telemetry are two different things.

Spying implies that some type of personal or compromising information is being gathered.

Is the electric company, phone company, your ISP, and your bank “spying” when it collects data about your usage?

JW the big difference IMHO, is you know what to expect when you make a deposit in your bank or cash a check. MS telemetry is still an unknown for even the most sophisticated IT folk. I am not worried about what the phone company collects as I still believe everything is still getting collected no matter what congress says.IMHO of course. Hopefully not a problem unless all goes to h3ii. And might just prevent that!

:cheers:

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

I did all those things jwoods and Sudo have been so kind to suggest and left the computer to download what I didn’t hide. It seemed that one, 3112343 especially, was related to W 10. I read all the descriptions hid some of them, and downloaded some since they didn’t seem to work one at a time. I don’t let anything update in general, btw, without seeing and choosing.

So I went through this whole process and got the “not genuine” notice again just now.. I’ll just have to start over, and fortunately made sure there was a restore point. Yes, Sudo, I did all that also as you describe below in #43. I’ll do my restore now and start over later. Grrrrrrrr! Thanks again for the tips; sorry to be such a pain, but I really appreciate the help.

Reply | Quote

Can’t understand why it wouldn’t install just one at a time if only one update was checked.

Of the 18 I got this month for my Win 7, I installed all but one for Skype and KB3112343 which I hid.

Reply | Quote

I think you should call Volume Licensing.

The update that triggers the license check may be a security update you need.

It may also happen again next Patch Tuesday with new updates.

I guess that will have to be my next step. I’m sure you know how people feel about Big Brother prying, I mean MS.

Reply | Quote

I tested the patches one at a time and found that KB3109094 triggered this. The other ten went through without creating this problem. Does someone know exactly what this patch contains that changes the validation?

Reply | Quote

I tested the patches one at a time and found that KB3109094 triggered this. The other ten went through without creating this problem. Does someone know exactly what this patch contains that changes the validation?

Thank you for pinpointing that particular update. I patiently downloaded each update, hiding this one that you identify. Thank goodness the “not genuine” notice never appeared again. It takes time b/c some of the updates require a restart and one has to wait for the whole process to finish after each update installs. I assume you had the “not genuine” problem too? On my list of things to do yet is to contact volume licensing at MS. I don’t know if they have any sympathy for someone who has no knowledge of a used computer having a volume license. If only they would be more open and honest about what their updates include.

Reply | Quote

Yes, I was aware of that but how does “graphics memory corruption” connect with “genuine” validation? Anyhow it seems to replace kb 3097877 on which I found http://www.infoworld.com/article/3004441/microsoft-windows/microsoft-surreptitiously-reissues-botched-patch-kb-3097877-for-windows-7.html

Reply | Quote

It doesn’t appear to be that random if whenever that update is installed it triggers the not genuine message.

Reply | Quote

Given that this appears to be a first for both members and many updates have flown under the bridge, why should a future update also trigger it ?

Reply | Quote

So why that particular update ?

Reply | Quote

So why that particular update ?

If it doesn’t have the yellow star or force you to actively run the WAT check, I very much doubt it’s the culprit.

Reply | Quote

It’s KB971033 that phones home which is the validation check.

Reply | Quote

I just reviewed all my notes. Early in the game, when I cliked on “more information” re 3112343, it was the only one that mentioned anything about W 10, so I hid it. Now I’m wondering about 3109094, b/c I didn’t want to risk downloading that one either, after what pernel said!

Reply | Quote

I just reviewed all my notes. Early in the game, when I cliked on “more information” re 3112343, it was the only one that mentioned anything about W 10, so I hid it. Now I’m wondering about 309094, b/c I didn’t want to risk downloading that one either, after what pernel said!

I think pernel was mistaken in suggesting KB3109094 to be the cause of his issue. As has been stated in #50, KB3109094 is part of this and the all of the files listed there as being replaced by that patch are GUI/display files, nothing listed that would be telemetry or WAT -related.

Reply | Quote

I guess the acid test would be to install it and see if the not genuine message returns.

Reply | Quote