Skip to content
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

Not able to inject LP and FOD #22

Open
AsmusRohwer opened this issue Feb 19, 2024 · 3 comments
Open

Not able to inject LP and FOD #22

AsmusRohwer opened this issue Feb 19, 2024 · 3 comments

Comments

@AsmusRohwer
Copy link

Hello,

first, thanks to hold wimwitch alive :)

here the issue:

i´m not able to inject windows 11 23h2 LP and FOD to the image.
If i try it i´ll get this error:
Error - Source not found. Please import some Demanding Features and try again
But the LP´s and FOD´s are still imported.

@AsmusRohwer
Copy link
Author

i found that if you select the Win 11 23H2 wim the wimwitchfk identify it as 22H2 but if you import the LP´s the folder name in imports->lang->windows 11 is 23H2. if you now rename it to 22H2 you will be able to select lp´s under customizations

@NytSong
Copy link

NytSong commented Mar 22, 2024

I tried renaming the folder to 22H2 but it still tells me that the source is not found.

Just to be sure, from the working folder it will be looking in .\imports\fods\Windows 11\22H2 ?

When I give it a source WIM to work with it shows Version: Unknown so I don't know if that's the problem.

Edit: Yeah. I had to make a folder called "Unknown Version"

FYI, I use the latest windows iso files via my visual studio subscription, meaning that this time I'm using the March 2024 update version of Windows 11 business editions, version 23H2

@mbradley73
Copy link

Same problem here. 4.0.1 imports, creates the directories under FoD, then go to select " Source not found. Please import some Demanding Features and try again " Tried the suggestion here of swapping the directory name to 22H2 instead of 23H2--didn’t work.

WimWitchFK shows the Source WIM as Unknown Version so if you create an Unknown Version directory under FoDS/Windows 11/Unknown Version and import, it lets you select .... same thing with the appx app removal text--you have to copy and rename the appx app removal to end with unknown version. But then you get a totally different error when you try to compile it due to the unknown version issue--at build time it errors saying, "ISO Binaries are not present for Windows 11 22H2", "Import ISO binaries from an ISO or disable ISO/upgrade Package creation." "Discarding WIM and not making it so."

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

No branches or pull requests

3 participants