Skip to content

New-OSBuildMultiLang.ps1 - Fix UpdateOS for Win11 #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

suazione
Copy link
Contributor

CU was never applied for Win11 because OSUpdate variable was always set to Windows 10. due to a small typo/bug where $WindowsImageMediaName was set to non-existing property of MediaName instead of ImageName (..\info\xml\Get-WindowsImage.xml)

@Simsi1986
Copy link

Simsi1986 commented Jun 10, 2023

Thx a lot, that you implemented some fix for that issue - I also did some investigation and could only recognize the root cause (wrong/different variables used), why your fix in the AllFunctions.ps1 was not used for New-OSBuildMultiLang.ps1. Unfortunately, I'm not so familar with Powershell to adjust existing scripts with that huge number of nesting and dependencies to do some adjustments like you did.

Therefore it's impressive that it's just that low code change, even if I can imagine that there was maybe some more effort to fire out that i's quite simple solution.

Just have tested it by changing local stored "New-OSBuildMultiLang.ps1" and can confirm it's working and approved the commit in Github - hopefully it will be included in OSDBuilder soon.

@suazione
Copy link
Contributor Author

Great, thanks for testing and verifying. :)

@Simsi1986
Copy link

@OSDeploy I know, you are busy and loaded with lots of other things, which is why I almost don't dare to ask. Could you kindly accept this pull request?

@OSDeploy
Copy link
Owner

OSDeploy commented Jun 25, 2023 via email

@Simsi1986
Copy link

I cross fingers, that your connection will be recovered soon.
Take the time you need, I just wanted to make you aware of this pull request.

@xe0n11
Copy link

xe0n11 commented Nov 21, 2023

+1 for having this accepted into the next build. 👍

@FLeven
Copy link

FLeven commented Jan 2, 2024

Could this also apply to 2022 Server ?

@Simsi1986
Copy link

@OSDeploy I know you're busy, but could you please just merge some of the highly requested pull requests which have been successfully tested like this one?

@FLeven I wouldnt expect that MultiLanguage will be available for Windows Server as even update for client OS is higly wanted since months. On the other hand I in general recommend to not use any other language than English for server OS for certain reasons - most are historical, but it's the IT language even if I know from our multi-country org that this is not common for all. We recently started to stick togeter cross-country wise with the decision that base language for all images will be English and the expectation is that everyone willing to work in IT is willing to at least be able to have some basic English skills in written form as most documentation in the web is in English as well (and I agree, even if it's not my mother tongue). I respect your request, it might be based on requirements which you haven't decided in your company.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants