Windows 8.1 Feature Pack kb2932046 (part of kb2919355) won't install

I have an 8.1 ISO, except fully expanded. I can't run setup because it asks me for a Windows 8.1 key and will not accept my 8 key. I've tried various dism options. Nothing happened, but I was never confident that what I ran was correct. If you'd like to make a suggestion as far as what I should run on the command line I'd be happy to try it. The 8.1 files live at H:\Windows81\ (e.g., that's where the setup.exe file is located).

I tried something similar with an ISO that I have using Powershell's equivalent to DISM and got a "not authorized".   FWIW I had noticed that it had an  Install.WIM  and was just trying to list its contents

OMG.  I can get into it!  Try this:

So, that would be H:  in your case.  I think where I went wrong after that is not understanding how to use the Index parameter.   But the output of this command at least now hints what it means.  See what you can get that way?

I took the Windows 8.1 Pro ISO, mounted and ran it.

I wonder if instead of running it you could have used it as a /source: for DISM?  I still think we (someone) have to figure out how to use that technique.  I think it might have avoided your (re-)activation problems for example.

Glad to see that you have a solution.  Thanks for sharing it.

I have an 8.1 ISO, except fully expanded. I can't run setup because it asks me for a Windows 8.1 key and will not accept my 8 key. I've tried various dism options. Nothing happened, but I was never confident that what I ran was correct. If you'd like to make a suggestion as far as what I should run on the command line I'd be happy to try it. The 8.1 files live at H:\Windows81\ (e.g., that's where the setup.exe file is located).

It would have been nice if only the corrupted file(s) had to be replaced. It would have gone a whole lot faster. Seems like the /source with DISM ought to work. Users would still have to obtain a "source" to initiate the repair, which is a big problem. No question that if MS starts offering repair/installation DVDs that I'll be getting one. I've learned a lot from your suggestions and others on the forums, but I really don't want to go through it again. The MS person who took care of my activation and the rest said that some of the issues were caused when people went from 8 to 8.1 . They saw that 8.1 was free on the store and just installed it. What they failed to do was run WU first. I got the impression that some had never run WU. That left 8.1 actually not installed properly.

Anyway, thanks again for your help. I guess this thread can probably be closed, if you have the authority to do that.

Jim

I took the Windows 8.1 Pro ISO, mounted and ran it.

I wonder if instead of running it you could have used it as a /source: for DISM?  I still think we (someone) have to figure out how to use that technique.  I think it might have avoided your (re-)activation problems for example.

Glad to see that you have a solution.  Thanks for sharing it.

SUCCESS

I took the Windows 8.1 Pro ISO, mounted and ran it. The installer started, briefly showing Windows 8, then kept going with the "waiting"  on screen. It did NOT ask for a product key, which surprised me. It evidently used the one already installed on my system. After about 5 minutes, I tried installing the KB2932046 which failed, then I tried again and it still failed so trying to "slip stream" that file didn't work. I chose to keep all settings, files and apps and then let the 8.1 installer continue and after about an hour the computer restarted and seemed to finish but stuck with a BSOD. I let it go for another 30 minutes with no change. I'd seen this before, so I shut off the power then rebooted. Seemed to be fine except now it asks for activation key. None I could fine would work, so I called Microsoft. The gentleman I talked with was VERY understanding. He took over the computer and got the verification part done. He then asked if he could go ahead and make sure Update 1 installed correctly. Windows Update installed 46 updates, some with the (for those without 2919355) notation. He restarted then came the KB2919355. Took another hour but it loaded using WU. In all, he spent about 2 hours getting Update 1 installed. Afterwards there were another 10 updates which went fine.

I ran DISM /scanhealth at the end and there is no longer any component store corruption. Now that the KB2932046 is installed, I still do not see any new features from before HOWEVER the features all work much more smoothly and quickly.

This was not a fun exercise. Using an ISO ( or DVD ) seems the only way to go once the corruption occurs and DISM can't fix it. All the more reason for manufactures and MS to make repair installation media easily available.

Hope this helps someone else.

Jim