Very strange scenario... particularly as you have "No SPP event log errors found!" in your report
If Windows is unable to activate itself it writes an event there...
I will be very interested in the MS support call... my re-collection of these incidents is usually they give up and dish out new key but perhaps things have changed now...
I don't know. This is NOT the temp key I mentioned (ending in 3V66T). It could be a Windows Family one:I bought the laptop with Family by mistake - I have no track of it though. I COULD uninstall Pro to get it, but...
I will certainly do. At this point, it was 20 hours without reset, so I have not called yet.
You cab get the full key by running licensingdiag.ps1 -show command
Then check what type of key it is with ShowKeyPlus "Check" function - will be interesting to see
Good news then - in 4 hrs time you will have a record - 1 whole day without deactivation
This is indeed the original Wondows 10 Family key from Dell:
ShowKeyPlus - Windows Product Key Information
Original Key: xxxxx-xxxxx-xxxxx-xxxxx-WTYK3
Original Edition: Win 10 RTM Core OEM:DM
EULA Type: OEM
I will now perform a series of cold reboot, wait another 24 hours and declare the issue solved if everything goes well. If so, this would mean that the sfc /scannow has done the job OR that a patch has done the job. Guess we will never now. If you are interested, I can send privately the relevant part of CBS.log
Gilbert
Cool... yes send me the log please.This is indeed the original Wondows 10 Family key from Dell:ShowKeyPlus - Windows Product Key Information
Original Key: xxxxx-xxxxx-xxxxx-xxxxx-WTYK3
Original Edition: Win 10 RTM Core OEMM
EULA Type: OEM
I will now perform a series of cold reboot, wait another 24 hours and declare the issue solved if everything goes well. If so, this would mean that the sfc /scannow has done the job OR that a patch has done the job. Guess we will never now. If you are interested, I can send privately the relevant part of CBS.log
Gilbert
Holding thumbs it's fixed now... :)
After 36 hours or so... "Activate Windows" is back, with the same symptoms.
I will definitively call MS on Monday.
G.
It's a shame....
I must say I do admire your perseverance - I would have made a backup of that system and cleaned installed by now.
But keep us posted.
Good luck.
@ghxyzzy
Something in the log you sent me points to pending updates...
Try running these commands after each other
Edit:Code:dism /online /cleanup-image /revertpendingactions sfc /scannow
Forgot to mention - don't force the activation - Windows must activate automatically.
Last edited by Superfly; 16 Nov 2019 at 14:27.
> dism
See attached relevant part of the log.
> sfc
"Windows Resource Protection did not find any integrity violations." However the log (partly attached) show a few warnings, including this one (which sounds strange):
2019-11-17 10:27:48, Info CSI 0000014f Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-shell32, version 10.0.18362.449, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-shell32, version 10.0.18362.449, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
> Forgot to mention - don't force the activation - Windows must activate automatically.
I don't understand. Do you mean I should not run slmgr -ato or similar?
Last edited by ghxyzzy; 17 Nov 2019 at 04:42. Reason: adding information
Quote