Solved Windows is activated delay :/

[ThrashZone]

Every time I go to control panel system and scroll down to the bottom it say "Status not available"
But a second later it say windows is activated ?
If I go back after the first time it still shows activated

Is this delay normal when going to system after startup,
Does anyone else see this delay in listing activated ?
Happens on both lappy 32 and desktop 64 bit :/
Very weird seems windows should be able to remember if it's been activated or not or genuine or not
Cheers.

 

[Berton]

I've seen it a lot, doesn't seem to be a problem. I just consider it being Windows reading itself before populating the panel. Also see it when right-clicking Computer/My Computer in the Start menu and choosing Properties.

 

[ThrashZone]

Thank you for confirming you see it too

 

[Berton]

You're welcome.

 

[carwiz]

My Genuine logo has a slight delay of probably less than half a second but it's noticeable. Never really paid attention to it. Must be some I/O going on to place the image there. I don't worry about such trivial things; I'm pondering what's for lunch.

 

[Berton]

Things like that are Dynamic, not Static like a picture on the wall. Even the Desktop is constantly refreshing/redrawing, just usually not noticeable.

 

[NoelDP]

The licensing system performs a check whenever the System page is opened, before it posts the Product ID, and the WGA Logo - it's this that delays the display a little.

 

[ThrashZone]

Thanks guys I always wondered if anyone else see the same thing,
Yes it is often a split second I can barely get to the last word before it changes
Cheers.

There's just been a lot of not genuine questions posted lately :/

 

[NoelDP]

The KB3004394 cockup still has to work its way out of the system - that accounts for half of current case.

 

[carwiz]

The KB3004394 cockup still has to work its way out of the system - that accounts for half of current case.

Awh, come on! MS fixed that one and it only took about four months. :shock:

https://support.microsoft.com/en-us/kb/3024777

 

[NoelDP]

Four days, actually!
The patch was first released on 10th December - and pulled within 24 hours.
They released the KB3024777 removal tool about 4 days later - but the problem was that about half the affected machines were blocked from actually downloading and running the tool.
MS has kept VERY quiet about that (I wonder why?).
The fixed KB3004394 patch wasn't released until the February season - and has worked fine, so far as I can tell.

 

[ThrashZone]

That's interesting I show KB3022777 not KB3024777
Installed on 1/13/15 :/
Don't show the other one so I guess it worked by the other KB# ?
I'll have to check my 32 bit system and see what it shows.

 

[carwiz]

Four days, actually!
The patch was first released on 10th December - and pulled within 24 hours.
They released the KB3024777 removal tool about 4 days later - but the problem was that about half the affected machines were blocked from actually downloading and running the tool.
MS has kept VERY quiet about that (I wonder why?).
The fixed KB3004394 patch wasn't released until the February season - and has worked fine, so far as I can tell.

That could be. I don't follow them that close. I was going by KB review date.

Article ID: 3024777 - Last Review: March 16, 2015 - Revision: 8.0

 

[ThrashZone]

I saw that revised date too but I have not got that update :/
My 32 bit laptop was reinstalled 2/28/15 and it has none of them ?

 

[NoelDP]

KB3024777 simply uninstalls KB3004394 - with the result that neither appear in the Installed Updates listing (until the new version of KB3004394 gets installed)
They may appear in the Update History list - 4394 should have a date between 9th Dec and 12th Dec.

 

[ThrashZone]

KB3024777 simply uninstalls KB3004394 - with the result that neither appear in the Installed Updates listing (until the new version of KB3004394 gets installed)
They may appear in the Update History list - 4394 should have a date between 9th Dec and 12th Dec.

Hi if you be so kind to take a peek in your free time,
sfc showed no errors,
Last go round with windows update showed error code 8024402c
I eventually unhide the win-10 KB3035583 recommended update then was Optional and hid KB 2990214 returned into an important one and was not listed in the hide list :/
But the error was solved for the most part rechecked for updates and all of this last round updates appeared,
I hid the 2 above updates and loaded the rest all loaded successfully

Now after running sfc I see
Check for updates for your computer
Most recent check for updates Never

Fortunately after clicking on the check for updates button on the message it did successfully check for updates without error

 

[NoelDP]

There's no errors in either CBS.log or the CBSPersist file.

Here's the official definition of our 8024402C code...
Winhttp SendRequest/ReceiveResponse failed with 0x2ee7 error. Either the proxy server or target server name can not be resolved. Corresponding to ERROR_WINHTTP_NAME_NOT_RESOLVED. Stop/Restart service or reboot the machine if you see this error frequently.

(p.s. - what free time? )

 

[ThrashZone]

Hee-hee
Man I removed an update just a bit ago,
KB3021917 issued 3-10-15
To send telemetry to M$ about upgrade... I didn't mind at the time because of the bricked hdd from testing win-10tp
But it seems all of this win-10 update stuff started back then,

These now after removing the above these two show back up,
KB3004375 and KB3031432
I remember these as Recommended when released and I hid both seeing one was more for turning on a feature close to an NSA snoop for home group.. surveillance :/
The another one was to fix the first
Either way both now are Important