Windows 11 CBS 25H2

Hi I keep seeing this group of messages in the CBS

Skip FODs not currently installed: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-OCR-en-gb-Package~31bf3856ad364e35~amd64~~10.0.26100.1, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.26100.1742, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-Basic-en-gb-Package~31bf3856ad364e35~amd64~~10.0.26100.1, state: Staged
Skip FODs not currently installed: Microsoft-Windows-LanguageFeatures-Basic-en-au-Package~31bf3856ad364e35~amd64~~10.0.26100.1, state: Staged
Skip FODs not currently installed: Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1742, state: Staged

I am in Australia, FOD's I believe is Feature on Demand.
The Windows install was done from a US ISO with Australia as the Location.
I am wondering why Windows keeps repeating this routine?
Have Ran as Admin DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /RestoreHealth and SFC /Scannow with no errors.

Regards EB2XR6.

EB2XR6 said:

Have Ran as Admin DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /RestoreHealth and SFC /Scannow with no errors.

Click to expand...

If everything is okay then why are you concerned about what it says in the log? Don't look. You will be happier not looking for trouble. Never trouble trouble until trouble troubles you.

As always "If it ain't broke -- don't fix it".

Cheers
jimbo

wiganken said:

If everything is okay then why are you concerned about what it says in the log? Don't look. You will be happier not looking for trouble. Never trouble trouble until trouble troubles you.

Click to expand...

jimbo45 said:

As always "If it ain't broke -- don't fix it".

Cheers
jimbo

Click to expand...

Thank you for the replies.
Windows 11 is repeating this operation constantly and I was hoping someone may be to explain why?
I have had a number of issues with Windows 11, the last one happened during a repair install for a reason I have no idea why, a second language version of Micrsoft 365 was installed, The ENG-US version installed and after the repair the ENG-GB was also installed.

EB2XR6 said:

Thank you for the replies.
Windows 11 is repeating this operation constantly and I was hoping someone may be to explain why?
I have had a number of issues with Windows 11, the last one happened during a repair install for a reason I have no idea why, a second language version of Micrsoft 365 was installed, The ENG-US version installed and after th365e repair the ENG-GB was also installed.

Click to expand...

Open a MS365 app (I used Outlook below) and navigate thus File => Options => Language



and remove those you don't require.

There's nothing wrong with CBS. When you install a Windows image, it has a number of "stub" packages to remind itself which FOD's exist for your Windows edition. Staged means DISM knows the feature exists, but it's not currently enabled.

According to you, the base install was en-US edition and en-GB was applied over it as a repair install. Now your Windows knows about en-US, en-GB and en-AU language FOD's. Since you now have "merged" image, it's safer to leave the en-US components in place.

A common mistake is for someone in Commonwealth country using the en-US ISO instead of the en-GB ("English International") edition.

garlin said:

There's nothing wrong with CBS. When you install a Windows image, it has a number of "stub" packages to remind itself which FOD's exist for your Windows edition. Staged means DISM knows the feature exists, but it's not currently enabled.

According to you, the base install was en-US edition and en-GB was applied over it as a repair install. Now your Windows knows about en-US, en-GB and en-AU language FOD's. Since you now have "merged" image, it's safer to leave the en-US components in place.

A common mistake is for someone in Commonwealth country using the en-US ISO instead of the en-GB ("English International") edition.

Click to expand...

Thank you Garlin, I wiped the Hard Drive and reinstalled using the en-GB ISO. Australia uses a US-keybaord layout there is 3 Languages installed to vaying degrees,

EB2XR6 said:

Thank you Garlin, I wiped the Hard Drive and reinstalled using the en-GB ISO. Australia uses a US-keybaord layout there is 3 Languages installed to vaying degrees,

Click to expand...

Further to my reply.
The Australian Govt website recommends using US International Keyboard Settings however when I do, the " ' characters do not display on Screen until I type the next character, however when using the US Keyboard setting " ' display when typed.
I did some reseaerch on the " ' are a known issue with the US International Keyboard Setting.

EB2XR6 said:

Further to my reply.
The Australian Govt website recommends using US International Keyboard Settings however when I do, the " ' characters do not display on Screen until I type the next character, however when using the US Keyboard setting " ' display when typed.
I did some reseaerch on the " ' are a known issue with the US International Keyboard Setting.

Click to expand...

I think US International keyboard layout has some dead keys in order to type accented Latin characters, similarly to Greek typing nothing when you press the ; (next to L) as it is the Greek accent and waits to press the vowel in order to display the respective accented vowel. Why use that? Add the "regular" US keyboard and remove the US International.

The preferred keyboard standard in Australia is the US International layout. But you don't need to install EN-US Windows in order to have it. Outside of the Windows Single Language edition, you can add extra language support (and keyboards) to an existing Windows.

The correct route would be to install EN-GB Windows, if you live in Australia, and then add the US Int'l keyboard after installation.

You don't install EN-US Windows simply to get an US keyboard. That's not how Windows designed support for additional locales.

EB2XR6 said:

I wiped the Hard Drive and reinstalled using the en-GB ISO

Click to expand...

I know it's too late now but Bree posted a method of resolving a language mixture without a re-install - running a Repair install using a desired-language ISO of the currently-installed Windows version.
Convert en-US to en-GB in a Repair install using the same version ISO - Bree post #34 - ElevenForum
I would guess that an MSOffice repair procedure might well avoid having to reinstall that afterwards.
Repair an Office application - MSSupport


Denis

I've got a long list of those Skip FOD listings in the cbs.log on my desktop PC which has a 3-week-old clean install of Windows 11 25H2. They don't read like they're error messages so I'm not going to worry about it. Most of the FOD listings are for features or devices I've disabled like the WiFi and the Sound Recorder.

It means afaik that a feature isn't installed.