search

alaurie / WimWitchFK

General clean up of WimWitch script before converting into a PowerShell module.
MIT License
68 stars 8 forks source link

" .Net 3.5 binaries are not present for 23H2. Import .net from an ISO or disable injection to continue." #36

Open rootabagga opened 3 months ago

rootabagga commented 3 months ago

We are unable to inject .Net Framework 3.5 into the wim file for Windows 11 23H2, despite the fact that the checkbox for "inject .Net 3.5" remains on the Customizations tab.

Expected Behavior

With the old WimWitch, we were successfully able to inject .Net Framework 3.5 into Windows 10 22H2 and Windows 11 22H2.

Current Behavior

When we click on the Make It So button, everything appears to work except for injecting .Net Framework 3.5. We get the error message in the subject line, and the processes for Make IT So are stopped, waiting for us to inject .Net Framework 3.5. Unfortunately, we still need to be able to inject .Net Framework 3.5 into the WIM file for Windows 11 23H2, as we still have applications using it, and the workaround to get .Net framework 3.5 installed is to remove the computer from the domain, install .Net Framework 3.5, then rejoin the domain . With Microsoft promising to stop supporting Windows 11 22H2 this fall, our IT Leadership team is getting nervous.

Possible Solution

Alex, is this something you are working on? If so, do you have a timeline on when this will be fixed? Or can you provide easy to follow instructions on how we might import .Net 3.5 from our ISO?

Steps to Reproduce (for bugs)

I finally figured out what you meant when you said that we can install WimWitchfk from the powershell gallery. That got WimWitchFK to load, and I was able to successfully update it to the latest version as well. All functionality looks good except for importing .Net Framework 3.5.

Context

We would like to be able to create a wim file for Windows 11 23H2 with .Net Framework 3.5 injected successfully.

Your Environment

chrisecklar commented 3 months ago

Workaround: Assuming you have the DotNet 3.5 binaries working in WimWitch for Windows 11 v22H2:

  1. Copy WimWitch\imports\DotNet\Windows 11\22H2 to 23H2.
  2. Verify the new folder name is just "23H2."
  3. Run WimWitch as normal and allow it to inject DotNet 3.5 into Windows 11 v23H2. image
NoDowt commented 1 month ago

Just started using WinWitchFK (Previous WimWitch user, but just start to look at Win11) and noticed when importing the 23H2 ISO, its importing it to a 22H2 folder... Most likely this is causing the problem here.

Logic in the script is probably looking for the 23H2 folder when applying, but the import is putting it into 22H2.