Windows 7 build 7601 not genuine message, slui will not run

[NoelDP]

Nothing sensible - I think I intimidate them
I was hoping that they'd pass me up the food-chain, but that hope seems forlorn now
Thanks for reminding me - I'll try posting a query somewhere else and see if that gets a better response.

 

[kylescf]

Thanks Noel
I don't know if you know anything about licences but you may have noticed this installation uses a MAK - a legal one. On the Open Licence Details it states it is active. The start date is 2011-01-20 and the end date is 2013-01-31. Do you know if this means that after the end date it will no longer work and we would have to get another one? I was just thinking about the ultimate solution of a clean install.

 

[NoelDP]

Volume Licenses are subscription, is my understanding.
Unless the subscription is renewed the License will lapse, and no new activations can take place with that Key, although validation may/should still pass.
This means that any scenario requiring re-activation will require a new Key.
Once Blocked, a Key will never be re-issued.

 

[kylescf]

OK, I thought it would be something like that. Thanks.

 

[NoelDP]

Can you upload the complete C:\Windows\Logs\CBS folder for me, please - I may have found someone who can trawl through the history and see what can be found.

 

[kylescf]

OK.

I had sent the CBS itself already but here is a up to date copy with all the other files in the folder too.

Wishing your trawler good luck!

 

[kylescf]

No I don't think I had sent it before - it's been a long day

 

[NoelDP]

You had sent the CBS.log file before - but there was nothing of note in it.
Hopefully the full set will include more data.
Thanks!

 

[NoelDP]

OK - we may be getting somewhere
I've got a couple of small scripts for you to run in Powershell (!)

I'll put the instruction for opening Powershell at the end.
Copy/paste each script (one at a time!) into the Powershell window - there will be a short lag, and then you'll get a mess of output (hopefully). Copy the output from each script to a separate reply, using the method in the instructions below.
(note that I've added a CLS clear screen command at the front of each script - so if you run them both at the same time, you'll only see the results from the second)

cls
$wmiObj = New-Object System.Management.ManagementClass SoftwareLicensingProduct
$LicenseStats = @("Unlicensed", "Licensed", "OOBGrace", "OOTGrace", "NonGenuineGrace", "Notification", "ExtendedGrace")
foreach($p in $wmiObj.GetInstances())
{
    "Name: {0}" -f $p.Name
    "GenuineStatus: {0}" -f ($p.GenuineStatus -eq 0)
    "LicenseStatus: {0}" -f $LicenseStats[$p.LicenseStatus]
    "PartialProductKey: {0}" -f $p.PartialProductKey
    "ProductKeyID: {0}" -f $p.ProductKeyID
    "ValidationURL: {0}" -f $p.ValidationURL
    "--------------------------------`n"
}

#2

cls
$wmiObj = New-Object System.Management.ManagementClass SoftwareLicensingProduct
$wmiProperties = $wmiObj.Properties 
"{0} Properties:`n" -f $wmiProperties.count 
 
foreach ($obj in $wmiProperties)
{
    "`tProperty Name: {0}" -f $obj.Name
}

Here are some instructions to make life easier
1) To open an Elevated PowerShell, click on Start, All Programs, Accessories, System Tools, Windows PowerShell – then right-click on Windows PowerShell, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the PS Window, click on the blue/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Blue/white icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.
(almost identical to the CMD prompt)

 

[kylescf]

Hi Noel, this looks like interesting stuff!

There was a problem with the first script. See below.

PS C:\Users\admin> $wmiObj = New-Object System.Management.ManagementClass SoftwareLicensingProduct
PS C:\Users\admin> $LicenseStats = @("Unlicensed", "Licensed", "OOBGrace", "OOTGrace", "NonGenuineGrace", "Notification"
, "ExtendedGrace")
PS C:\Users\admin> foreach($p in $wmiObj.GetInstances())
>> {
>>     "Name: {0}" -f $p.Name
>>     "GenuineStatus: {0}" -f ($p.GenuineStatus -eq 0)
>>     "LicenseStatus: {0}" -f $LicenseStats[$p.LicenseStatus]
>>     "PartialProductKey: {0}" -f $p.PartialProductKey
>>     "ProductKeyID: {0}" -f $p.ProductKeyID
>>     "ValidationURL: {0}" -f $p.ValidationURL
>>     "--------------------------------`n"
>> }
>>
Name: Windows(R) 7, OCUR add-on for Ultimate,HomePremium,Enterprise,Professional,ServerHomePremium,Embedded
GenuineStatus: True
LicenseStatus: Unlicensed
PartialProductKey:
ProductKeyID:
ValidationURL:
--------------------------------

An error occurred while enumerating through a collection: .
At line:1 char:8
+ foreach <<<< ($p in $wmiObj.GetInstances())
    + CategoryInfo          : InvalidOperation: (System.Manageme...bjectEnumerator:ManagementObjectEnumerator) [], Run
   timeException
    + FullyQualifiedErrorId : BadEnumeration

PS C:\Users\admin>
PS C:\Users\admin>

Maybe that was supposed to happen?
The second one worked OK, I think.

PS C:\Users\admin> $wmiObj = New-Object System.Management.ManagementClass SoftwareLicensingProduct
PS C:\Users\admin> $wmiProperties = $wmiObj.Properties
PS C:\Users\admin> "{0} Properties:`n" -f $wmiProperties.count
44 Properties:

PS C:\Users\admin>
PS C:\Users\admin> foreach ($obj in $wmiProperties)
>> {
>>     "`tProperty Name: {0}" -f $obj.Name
>> }
>>
        Property Name: ApplicationID
        Property Name: Description
        Property Name: DiscoveredKeyManagementServiceMachineName
        Property Name: DiscoveredKeyManagementServiceMachinePort
        Property Name: EvaluationEndDate
        Property Name: ExtendedGrace
        Property Name: GenuineStatus
        Property Name: GracePeriodRemaining
        Property Name: ID
        Property Name: IsKeyManagementServiceMachine
        Property Name: KeyManagementServiceCurrentCount
        Property Name: KeyManagementServiceFailedRequests
        Property Name: KeyManagementServiceLicensedRequests
        Property Name: KeyManagementServiceMachine
        Property Name: KeyManagementServiceNonGenuineGraceRequests
        Property Name: KeyManagementServiceNotificationRequests
        Property Name: KeyManagementServiceOOBGraceRequests
        Property Name: KeyManagementServiceOOTGraceRequests
        Property Name: KeyManagementServicePort
        Property Name: KeyManagementServiceProductKeyID
        Property Name: KeyManagementServiceTotalRequests
        Property Name: KeyManagementServiceUnlicensedRequests
        Property Name: LicenseDependsOn
        Property Name: LicenseFamily
        Property Name: LicenseIsAddon
        Property Name: LicenseStatus
        Property Name: LicenseStatusReason
        Property Name: MachineURL
        Property Name: Name
        Property Name: OfflineInstallationId
        Property Name: PartialProductKey
        Property Name: ProcessorURL
        Property Name: ProductKeyID
        Property Name: ProductKeyURL
        Property Name: RequiredClientCount
        Property Name: TokenActivationAdditionalInfo
        Property Name: TokenActivationCertificateThumbprint
        Property Name: TokenActivationGrantNumber
        Property Name: TokenActivationILID
        Property Name: TokenActivationILVID
        Property Name: TrustedTime
        Property Name: UseLicenseURL
        Property Name: VLActivationInterval
        Property Name: VLRenewalInterval
PS C:\Users\admin>

 

[NoelDP]

That confirms that you have corruption in the WMI process somewhere - we need to work out where....

back as soon as I get an analysis !

 

[kylescf]

That's encouraging. I hadn't known about Powershell before. I'm glad we had a BASH at it! (Sorry - shouldn't make Linux jokes on a Windows site).

 

[NoelDP]

Why not? I have Penguins for breakfast snacks

 

[kylescf]

Hi Noel,

Any luck with an analysis?

 

[NoelDP]

Ooops! - I must admit I'd forgotten all about it :blush:

I'll chase and do some of my own research.

 

[kylescf]

That's OK. I know you must be very busy and your help is appreciated.

 

[NoelDP]

I've pinged the guys, but not heard back yet.
Looking at your error, it appears to be rare, and related to the WBEM repository.
Please run the following commands...

DIR C:\Windows\System32\wbem /S >>%userprofile%\desktop\npwmi.log
ICACLS C:\Windows\System32\wbem\Repository /T >>%userprofile%\desktop\npwmi.log

They should create a new file - npwmi.log - on the desktop - please attach the file to a response.

 

[kylescf]

OK that's done - file attached.

 

[NoelDP]

That all looks normal to me.
back to the thinking-platform