Solved Newbie.....operation failed with 0x8007047f.... i cant install wmp!!!

[moogwai]

Hi guys....newbie here. I recently had to format my pc and install a new copy of windows 7 as i had constant crashing of my pc.

I brought a new copy of windows 7 and apparantly its a "n" version.

I'm trying to install wmp 12 and ive downloaded the media pack update thing from the windows update section but media player doesn't install!! so i try to install wmp 11 and get the "operation failed with 0x8007047f" error code!! its doing my head in a bit now.....so does anyone know how to get around this??

your help will possibly stop me from going bald!!!

thanks guys.

 

[marsmimar]

Hello moogwai and welcome to Seven Forums.

Just for clarification, is this where you downloaded the Media Feature Pack? The download link is near the bottom of the KB article.

Description of the Windows Media Feature Pack for Windows 7 N and for Windows 7 KN

You may have to go into Windows Update History to see if any previous attempts to update WMP are showing. If yes, I'd suggest uninstalling first before attempting any new install of the Media Feature Pack.

http://www.sevenforums.com/tutorials/24373-windows-update-uninstall-update.html

 

[moogwai]

thanks Marsmimar, yes thats where i downloaded the media pack.....i checked the windows update history and there were no signs of any attempt to update wmp.

when i attempt to install the update package it comes up with the screen shot ive attached

 

[marsmimar]

I don't know if this will make any difference, but let's try running a system file checker scan from an elevated command prompt (option two, this tutorial.) Perhaps there are damaged or corrupt system files that are preventing the Media Feature Pack from installing. If problems are found, run the scan 3 times rebooting in between each scan.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[karlsnooks]

moogwai,
Where did you buy your Win 7?

 

[moogwai]

I don't know if this will make any difference, but let's try running a system file checker scan from an elevated command prompt (option two, this tutorial.) Perhaps there are damaged or corrupt system files that are preventing the Media Feature Pack from installing. If problems are found, run the scan 3 times rebooting in between each scan.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

i ran the system file checker and it found no problems!! grrr

 

[moogwai]

moogwai,
Where did you buy your Win 7?

i brought it from a verified seller on play.com......should i contact him about it? i have verified windows 7 and it it seems fine

 

[Golden]

Hi moogwai,

If you like, we can check your Windows 7 for you before you contact the seller.

Please perform the following:

1. Download and save this tool to your desktop:
http://go.microsoft.com/fwlink/?linkid=52012

2. Run the tool, and then click 'Copy' - ignore any errors if they appear

3. Use CTRL+V to paste the unedited results of the validation tool here in your next reply

http://www.sevenforums.com/windows-...ne-activation-issue-posting-instructions.html

Regards,
Golden

 

[karlsnooks]

Definitely follow the suggestion from Golden. That version is not meant for sale to individuals.
Next time you want to buy Win 7 then go to a store which will be offering Win 7 in a Microsoft-logoed package from Microsoft.

Did your computer come with Win 7? Yes/no.

 

[moogwai]

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-GD7C6-77CT4-TVG39
Windows Product Key Hash: 4Lpd7Dzu0Xx/k5e9qqh11gsYjmw=
Windows Product ID: 00432-076-9822597-86623
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.028
ID: {D37D9AEE-2096-4053-B985-9ECB064F0E10}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows 7 Ultimate N
Architecture: 0x00000000
Build lab: 7601.win7sp1_gdr.120330-1504
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{D37D9AEE-2096-4053-B985-9ECB064F0E10}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.028</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-TVG39</PKey><PID>00432-076-9822597-86623</PID><PIDType>5</PIDType><SID>S-1-5-21-574713589-65372721-1144747039</SID><SYSTEM><Manufacturer>Unknow</Manufacturer><Model>Unknow</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="5"/><Date>20080709000000.000000+000</Date></BIOS><HWID>8A373407018400F4</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, UltimateN edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: dca01e19-01f5-4ce1-98b1-35fb7a323806
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00432-00172-076-982259-00-2057-7601.0000-2462012
Installation ID: 000044174822306724567372271671894724948223914964716782
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: TVG39
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 13/09/2012 10:49:24
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
 
HWID Data-->
HWID Hash Current: MAAAAAEABAABAAEAAAABAAAAAQABAAEAJJSyrPyLkKZsvbiRfI3O5lx7GuyEOhh5
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
ACPI Table Name OEMID Value OEMTableID Value
APIC RS690 AWRDACPI
FACP RS690 AWRDACPI
HPET RS690 AWRDACPI
MCFG RS690 AWRDACPI

i think i have done it right!!

 

[Golden]

<Date>20080709000000.000000+000</Date>

<SYSTEM><Manufacturer>Unknow</Manufacturer><Model>Unknow</Model>

Hi,

There isn't something quite right here - notice your date precedes the release date of Windows 7 - this isn't possible. Also, notice the obvious spelling errors in red above.

I've requested NoelDP to have a look at this a bit more as he has far more experience than me at this, but at the moment I suspect this installation counterfeit.

Regards,
Golden

 

[NoelDP]

There's no problem with the report - Retail Keys are independent of manufacture date and SLIC table.


It appears to me to be a standard Retail Key - it's certainly not a known MSDN one (but I don't know any Ultimate N MSDN CID's), and it's not an OEM one of any kind.

I have to admit to being a little surprised - play.com is almost as bad as eBay for piracy problems.

How did the package arrive?? - please see the following, just in case.........



http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/a2444f34-0aff-4f29-a8ac-67e28b0c0285

and

http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/309bb621-92d5-43d6-98c1-2bb51b35607f

The pirates have got VERY good at this over the past few years, as the price of equipment for manufacturing the packages drops, and as factories open in less well-policed countries.

see also this post....

http://social.microsoft.com/Forums/en-US/genuinewindows7/thread/46a58748-5a64-41ff-b7f4-f6d3b47beca9


Also - have a look at this video....


http://www.youtube.com/watch?v=hzqNNiOM0c

 

[Golden]

Thanks Noel. I'm surprised you don't see the date as an issue though?

 

[NoelDP]

Nah - it's only ever an issue with OEM_SLP Keys (and by inference OEM_COA_SLP Keys) - Retail, and OEM_NSLP keys don't even look at the SLIC table.
The BIOS date canonly be an indicator at best - you can have two identical machines from the same manufacturer, both may have a BIOS date of 11/11/11 - one has may have a Win7 SLIC table, while the other doesn't. The difference is that the second one shipped with Linux installed, rather than Windows.
Conversely, you can have two identical (apparently) machines with SLIC 2.1 tables - with a BIOS date of 11/01/10 the other with a date of 08/08/09 - the second could be genuine, while the first could be counterfeit (BIOS updated to one released after Win7 launched, but SLIC table simulated by a loader.

Fun, ain't it - and people wonder why I can't produced a Flow-diagram of how to read an MGADiag report!?!

 

[karlsnooks]

Noel,,
What say you to the spelling errors?

 

[NoelDP]

Dyslexia lures?
Which ones?

 

[karlsnooks]

Highlighted in red in Post #11

 

[NoelDP]

doesn't make a blind bit of difference for a Retail key

 

[NoelDP]

...in fact, thinking about it, that information is ignored by ALL installations - because it's easily customer moddable.
There are any number of programs available on the internet to change DMI info - which is why it's flagged often as being unreliable. I've seen one or two reports where the data has been customised, but I can't remember offhand whether the Key was OEM or Retail (or what sort of OEM)

 

[karlsnooks]

I find it very unusual and very suspicious.

I say "counterfeit".