No (or I can't find) sources/sxs folder on my computer - Windows 10
I'm trying to install .Net 3.5 on Windows 10 and I've found that there's no sources/sxs folder anywhere on my computer.Either that or I'm too stupid to find it . Even when I try to download .Net 3.5 through Windows Features on my Control panel it can't find the sources
My internet is working fine and I've done that whole thing with the group policy editor so I have no idea where to go from here.
windows-10 .net-framework .net-3.5
add a comment |
I'm trying to install .Net 3.5 on Windows 10 and I've found that there's no sources/sxs folder anywhere on my computer.Either that or I'm too stupid to find it . Even when I try to download .Net 3.5 through Windows Features on my Control panel it can't find the sources
My internet is working fine and I've done that whole thing with the group policy editor so I have no idea where to go from here.
windows-10 .net-framework .net-3.5
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually../Windows/WinSxS/...
not../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20
add a comment |
I'm trying to install .Net 3.5 on Windows 10 and I've found that there's no sources/sxs folder anywhere on my computer.Either that or I'm too stupid to find it . Even when I try to download .Net 3.5 through Windows Features on my Control panel it can't find the sources
My internet is working fine and I've done that whole thing with the group policy editor so I have no idea where to go from here.
windows-10 .net-framework .net-3.5
I'm trying to install .Net 3.5 on Windows 10 and I've found that there's no sources/sxs folder anywhere on my computer.Either that or I'm too stupid to find it . Even when I try to download .Net 3.5 through Windows Features on my Control panel it can't find the sources
My internet is working fine and I've done that whole thing with the group policy editor so I have no idea where to go from here.
windows-10 .net-framework .net-3.5
windows-10 .net-framework .net-3.5
edited Jun 14 '17 at 15:26
fixer1234
18.7k144982
18.7k144982
asked Aug 17 '16 at 8:33
Alyssa-Belle CandelariaAlyssa-Belle Candelaria
6112
6112
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually../Windows/WinSxS/...
not../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20
add a comment |
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually../Windows/WinSxS/...
not../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually
../Windows/WinSxS/...
not ../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually
../Windows/WinSxS/...
not ../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20
add a comment |
2 Answers
2
active
oldest
votes
How did you install your Windows 10? If, for example, it was a USB drive with letter E: the following should be sufficient:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:sourcessxs
The file that needs to be in the sxs folder is called microsoft-windows-netfx3-ondemand-package.cab
A different trick is described on Technet:
https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/
In a PowerShell administrator prompt use the following command:
Add-WindowsCapability –Online -Name NetFx3~~~~
add a comment |
Make sure the windows update service isn't disabled. The brain trusts here had it disabled via gpo
Chris
add a comment |
protected by Community♦ Oct 24 '18 at 16:33
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
How did you install your Windows 10? If, for example, it was a USB drive with letter E: the following should be sufficient:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:sourcessxs
The file that needs to be in the sxs folder is called microsoft-windows-netfx3-ondemand-package.cab
A different trick is described on Technet:
https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/
In a PowerShell administrator prompt use the following command:
Add-WindowsCapability –Online -Name NetFx3~~~~
add a comment |
How did you install your Windows 10? If, for example, it was a USB drive with letter E: the following should be sufficient:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:sourcessxs
The file that needs to be in the sxs folder is called microsoft-windows-netfx3-ondemand-package.cab
A different trick is described on Technet:
https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/
In a PowerShell administrator prompt use the following command:
Add-WindowsCapability –Online -Name NetFx3~~~~
add a comment |
How did you install your Windows 10? If, for example, it was a USB drive with letter E: the following should be sufficient:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:sourcessxs
The file that needs to be in the sxs folder is called microsoft-windows-netfx3-ondemand-package.cab
A different trick is described on Technet:
https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/
In a PowerShell administrator prompt use the following command:
Add-WindowsCapability –Online -Name NetFx3~~~~
How did you install your Windows 10? If, for example, it was a USB drive with letter E: the following should be sufficient:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:sourcessxs
The file that needs to be in the sxs folder is called microsoft-windows-netfx3-ondemand-package.cab
A different trick is described on Technet:
https://blogs.technet.microsoft.com/mniehaus/2015/08/31/adding-features-including-net-3-5-to-windows-10/
In a PowerShell administrator prompt use the following command:
Add-WindowsCapability –Online -Name NetFx3~~~~
edited Jan 17 at 16:29
Janis Veinbergs
2171312
2171312
answered Feb 27 '17 at 10:08
mcedamceda
1112
1112
add a comment |
add a comment |
Make sure the windows update service isn't disabled. The brain trusts here had it disabled via gpo
Chris
add a comment |
Make sure the windows update service isn't disabled. The brain trusts here had it disabled via gpo
Chris
add a comment |
Make sure the windows update service isn't disabled. The brain trusts here had it disabled via gpo
Chris
Make sure the windows update service isn't disabled. The brain trusts here had it disabled via gpo
Chris
answered Apr 26 '18 at 21:28
Chris DalyChris Daly
1
1
add a comment |
add a comment |
protected by Community♦ Oct 24 '18 at 16:33
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
So mount a Windows 10 .ISO and point DISM to it instead of your local SxS, which if it is missing, means Windows will be unable to repair itself so that is a problem you should figure out. Of course the correct location is actually
../Windows/WinSxS/...
not../sources/sxs/..
– Ramhound
Aug 17 '16 at 10:20