Install Framework 3.5
Klacee Sawatzky
You may see the following configuration dialog if you try to run an app that requires .NET Framework 3.5. Choose Install this feature to enable .NET Framework 3.5. This option requires an Internet connection.
The .NET Framework is created by Microsoft and provides an environment for running applications. There are different versions available. Many companies develop their apps to run using the .NET Framework, and these apps target a specific version. If you see this pop-up, you're trying to run an application that requires .NET Framework version 3.5, but that version is not installed on your system.
You don't need to select the child items for Windows Communication Foundation (WCF) HTTP Activation and Windows Communication Foundation (WCF) Non-HTTP Activation unless you're a developer or server administrator who requires this functionality.
If you still can't resolve your installation issue or you don't have an Internet connection, you can try installing it using your Windows installation media. For more information, see Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM). If you're using Windows 7, Windows 8.1, the latest release Windows 10, or Windows 11, but you don't have the installation media, create an up-to-date installation media here: Create installation media for Windows. Additional information about Windows 11 and Windows 10 Features on Demand: Features on Demand.
If you're not relying on Windows Update as the source for installing .NET Framework 3.5, you must ensure to strictly use sources from the same corresponding Windows operating system version. Using sources from a different Windows operating system version will either install a mismatched version of .NET Framework 3.5 or cause the installation to fail, leaving the system in an unsupported and unserviceable state.
Following the guide (Windows 11 Installation on the Framework Laptop DIY Edition - Framework Guides) I used the media creation tool on a usb stick. The install on the laptop with that worked until the wifi connection screen during the setup process.
Got it, that seems to have worked.
The guide mentions that there is a workaround for needing a network connection, I assumed it should just work from the point before. Might be good to rephrase that a bit if someone from the team sees this.
Precisely, as Ian is asking if you made a Windows install boot drive then the necessary drivers to run setup and install the necessary files are already present. Once Windows is installed, as per the Framework instructions, you will need to install the Framework Windows Driver pack. This will ensure all devices work as they should and you will be good to go at that point.
Eventually, I gave up and ended up launching the windows 11 setup.exe from within my installed Windows 10. All in all, pretty frustrating (and I really wish I could just use this as my Linux machine).
In order to install Windows onto the expansion card, it is necessary to manually create the required partitions, then copy the Windows image over manually. This manual process is entirely accomplished from within the Windows installer itself, by dropping into a command prompt rather than installing graphically as usual.
Once booted into the Windows installer, proceed page by page until you have accepted the license agreement, then on the next page hit Shift+F10 to open a command prompt.
From this point on, ignore the graphical installer, everything will be done manually via the command prompt.
In my case, running Debian Bullseye on my internal drive, I ran the sudo update-grub command and it automatically generated a grub boot menu entry for the Windows Boot Manager. This allows for choosing which OS to boot without having to manually override using the F12 key.
So from the sound of it, if you were to install Windows 10 Pro with /Apply-Image above and then leave this as /index 1, if you were to eventually restore your OS via the recovery partition you would have your install changed to Windows 10 Home
You can then boot back into the Windows installer, repeat the assign letter="" commands from Partition the disk (it seems to forget a few of the letters when you exit the installer), then continue to Copy Windows data to the newly created partitions.
The only difference now is that instead of copying install.esd from X:\sources\ you copy it from your primary Windows partition - in the guide this is W:\ but for me it was C:\. After that I was able to follow the rest of the steps without any hiccups.
And that was it! After Rufus was done, I unplugged my storage card from the other machine and put it back in my framework laptop. I turned it on, spammed f12, selected the storage card as my boot media, and voila: I was in Windows.
I looked carefully in the forum and was surprised to see that there was no post with guidance on how to do this (only posts on people facing issues during/after doing it). I am looking to install Zorin OS but I believe this will be applicable to any Linux OS.
The feature still does not install even when I direct it to the SXS folder. I have program that use the 4.8 and the 3.51 together. I need to test this to get my companies programs to be certified. Anyone have any ideas. And Yes I have tried the DISM command line entry. Still no good.
.NET Framework 3 is still available, but it is not present on the sources of the installed OS. For standard Windows 10, it is download upon request by Windows. On Windows Server 2022, you need to get it from the installation iso/DVD.
2. In there, select the .NET Framework 3.5 and 4.8 (4.8 can be skipped, but recommanded) and enable all the feature and the subfeatures. (For advanced users, some subfeatures can be skipped, if truly unneccesary) It is pretty recommended to check on the features page DirectPlay, (it contains legacy Direct X, from before Windows 10, in a way, it is required by some components of .NET Framework. Also, there is Windows 10 Identity Foundation 3.5, since it is also a part of .NET Framework 3. You will get to a page with several components (I do not remember it what it says exactly, I rarely use it), there you shall a group of options labeled Application Developement. I suggest you check all things in there, since they are all related to .NET Framework. Of course, if you are an advanced user and know exactly what each one does and some are unneccesary, some of those can be skipped.
3. When you get to Confirm Installation Selection you need to check Specify Alternate Source Path. You need to acces the WS 2022 installation DVD or mounted or unzipped iso installation USB drive and go to the Sources and then Sxs in Sources. Get the adress in Windows Explorer and add it to Specify Alternate Source Path. This is the most important step.
If you have tried these steps precisely and installation fails, please be more specific about your experience. Tell us what exactly you did (i.e. where you obtained the sources and how exactly you specified the path) and what was the outcome. If there was an error message, please copy it as is, preferably via text. (But a screenshot would also do.) Thank you for providing the feedback!
I am using Ventoy to install the LTSC edition of Windows 10 (this is the version of Windows often installed on kiosks, etc. to avoid the bloat). This is an official Windows iso and I have successfully installed it on a Virtualbox guest on my Linux installation, so I have confirmed that the iso itself works.
During installation I am getting a prompt to browse for missing drivers on the installation of Windows 10. I know about the Framework driver bundle, but this is for post-install and the Windows installer does not understand the format of those drivers as one big .exe file.
I tried live booting from Ventoy to Ubuntu and it worked fine. Since I was getting errors on the Primary Partition, I went ahead and used GParted from Ubuntu to reformat the primary partition as NTFS just to have a clean slate for my next attempt, but it was of no help.
Looks like it is accepting a vanilla Windows install but only if that vanilla windows was from the Media Creation Tool. Personally, I am willing to fiddle around with manually installing drivers, etc. if it results in a better final result but it looks like whatever it is was producing problems.
I wonder if this issue could be resolved by merely bundling the Framework Driver pack as a zip file that I could unzip and put on a USB drive to browse for during install rather than an exe that depends on a completed install first.
I had that same error when installing Windows 11 during my last two installations. I found that if I got to that error, backed all the way out into the main menu, then tried to install again it would just work. Not sure why but it has happened twice now (with my Dell tower and my Framework Laptop).
This message can appear for a number of reasons unrelated to a missing driver. A common one is a version mismatch in the setup files. For example, if you applied a Setup DU such as KB5007402 to sources/ on the installation media, you also have to apply the same update to the Setup image inside sources/boot.wim:2. If you were not applying any updates, the files can just be missing or otherwise damaged.
I am having the same issue. I spent a few hours yesterday trying to figure this out but I am still pretty new to Linux so have not had any luck yet. If I figure things out or find a more detailed guide I will share.
Has anyone been able to get this to work with kali? I moved the new driver over to /lib/firmware and disabled the default all fine. I am able to see networks only after turning wifi off and back on in the setting and cannot connect to any. Any thougths?
i have Intel Wi-Fi 6 AX200 , how do i know the version of my driver , can u write that command line in the 5 step for me ( im Linux beginner and my english is not good sorry ) , have been stuck with no wifi adapter found for 3 days
c80f0f1006