Download Microsoft-windows-netfx3-ondemand-package.cab

[Faustina Bartsch]

Icannot find microsoft-windows-netfx3-ondemand-package.cab in C drive nor have I been successful at finding the answer in web searches. I can see other people mentioning it, but no one saying how to obtain the file?

I am not looking to inject it in an OSD. Just want to deploy this .NET 3.5 because with SCCM controlling windows updates, I can't even download it via Windows Features. I have had an experience where I tried to deploy an app, following instructions on , to find out later some steps were incorrect. There are not a lot of sources out there for deploying .NET 3.5.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Thank you so much for your answer. I followed the first link. When I tested this command dism /online /add-package /packagepath:microsoft-windows-netfx3-ondemand-package.cab , it resulted in error 0x80070002 on my end, but this command worked DISM.exe /online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"source location", so I ended up using the latter instead. I was able to enable .NET 3.5 feature successfully.

Morning all,

I'm running into an odd problem with my SCCM OSD TS. I am using MDT integration and have selected the steps Install Roles and Features to install the .NET Framework 3.5. I have this step right after the Setup Windows and Configuration Manager step. However, upon OSD completion, the process is not complete.

I also use MDT; however, I use a TS after the section in MDT called "State Restore". It is just before I start installing applications. My ps1 is the same as above (minus the Import command). I have the cab file "microsoft-windows-netfx3-ondemand-package.cab" and ps1 in the same source folder. The TS is straight forward.

Microsoft-windows-netfx3-ondemand-package.cab issues are often the result of the file that is missing, deleted, or accidentally moved from Windows 10 Features on Demand x86's original installed location. Obtaining a new, uninfected copy of your CAB file will usually resolve the problem. As a last measure, we recommend using a registry cleaner to repair any invalid microsoft-windows-netfx3-ondemand-package.cab, CAB file extension, and other file path references which could be causing the error message.

Most of your microsoft-windows-netfx3-ondemand-package.cab problems should be resolved if the file is placed in the correct file path directory, but it's a good idea to verify it is fixed. Test the outcome of the file replacement by loading Windows 10 Features on Demand x86 to see if the error still appears as it did before.

These CAB error messages can appear during program installation, while a microsoft-windows-netfx3-ondemand-package.cab-related software program (eg. Windows 10 Features on Demand x86) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. It's important to document when microsoft-windows-netfx3-ondemand-package.cab issues happen, as it helps troubleshoot Windows 10 Features on Demand x86 problems (and report to Microsoft).

These microsoft-windows-netfx3-ondemand-package.cab troubles are created by missing or corrupt microsoft-windows-netfx3-ondemand-package.cab files, invalid Windows 10 Features on Demand x86 registry entries, or malicious software.

3a8082e126