mum microsoft update package ?

Rbcc · Friday at 3:38 PM

Processing 1 of 1 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~et-EE~10.0.26100.1
[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
on Done
I opened one of these cab files with WinRAR and there was a bunch of mum files, does 7zip open the mum files. If I figure out what it is inside of these files where do I extract them to on the mounted image in windows?

garlin · Friday at 3:53 PM

Why do you need to add this package?

1. WinPE-NetFx-Package~31bf3856ad364e35~amd64~et-EE~10.0.26100.1 only applies to boot.wim.

2. This package adds Estonian language support for .NET 3.5 error reporting for developers. If you're not running a .NET 3.5 app from inside WinPE, you don't really need this integrated into WinPE.

3. Adding this localization CAB requires the base WinPE-NetFx-Package to be installed first. That OC is not included on the LSOF ISO, and must be downloaded from the Windows ADK WinPE Add-on installer.

Rbcc · Friday at 4:10 PM

Is that the WinPE-Dot3Svc_Et-ee.cab out of the WinPE? and for every other language?

garlin · Friday at 6:23 PM

Read the WinPE Optional Components doc before trying to add random features. You can’t add any localization CAB’s until the base OC CAB is added to WinPE. In Windows, there is normally a language-neutral base, and other languages applied on top of the base.

Rbcc · Sunday at 3:24 PM

OC CAB = WinPE-DismCmdlets?

garlin · Sunday at 5:06 PM

That’s one of OC’s available to install. What’s the real question? You should read what the MS doc says about each OC and all the special notes like a list of required pre-requisites.

Rbcc · Sunday at 9:08 PM

Okay after reading the it says you have to install winpe wmi . There is one for each of the languages and on down at the bottom of directory of windows preinstall environment/OC's which one do I install???

pseymour · Sunday at 9:18 PM

You're all over the place with these cabinet files. First, .NET Framework, then 802.1x stuff, then DISM, now WMI?

What is it you're actually trying to accomplish?

garlin · Monday at 12:08 AM

It's a random walk through the LSOF ISO.

Rbcc · Monday at 2:15 AM

What I am doing is trying to figure why I keep getting a "not applicable to this image" error when I try to install setup.xxx and legacy setup in boot.wim. I am using the OC's from \Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs.

garlin · Monday at 9:42 AM

Problems with 24H2 autounattend install with config set

Rbcc · Monday at 5:03 PM

Great Support, Is there no solution?
JTM

garlin · Monday at 6:58 PM

What do you mean? You follow the posted instructions which forces legacy Setup client to always run on a 24H2 ISO install.

There's no need to install any WinPE OC's, unless you are scripting a custom WinPE install that doesn't go through normal Setup. For most users, switching to the legacy Setup client fixes most of their 24H2 compatibility issues where something worked before in 23H2. After adding the registry value to boot.wim, it works exactly as before with just ONE edit and no other unknown mods to Windows.

Rbcc · Monday at 7:54 PM

Posted instructions? Send a like so I can follow them! J

garlin · Monday at 7:58 PM

Did you not click the link from post #11? That's the complete instructions right there.

mum microsoft update package ?

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

enjoying a tall glass of Tang

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Similar threads