About two three weeks ago that I get a request to install a software on one of the Win10 computers. The software require computer to run .net 3.5. and the .net 3.5 was pushed to the computer by SCCM, however it keep give me error message. I tried to install it manuly with GUI at first. but It also been blocked by our firewalls. I could not donwoad the reqiure file for .net 3.5 from MS. Therefore , I was trying to see if I could download the .net 3.5 file and install it offline..
How to offline install .NET 3.5 on Win10 computers?
after tried serval different ways inclduing download installation file from MS but still can’t install it due to blocked by firewalls and things. Howevere very lucky that I found I could donwload a CAB file “microsoft-windows-netfx3-ondemand-package.cab” and install from it offline.
simply copy the CAB file to one of the folder (in my case is C:\Utility\) then run CMD as Admin and run the following commned. It will then install and enable .Net3.5 for you
WSL ( Windows Subsystem for Linux ) is a very nice and good practice environment on Windows 10 for people who would like to taste a bit of linux system and bash…etc you could turn on the feature and install the supported Linux you like. currently supported Linux as follow:
Ubuntu 18.04 Ubuntu 18.04 ARM Ubuntu 16.04 Debian GNU/Linux Kali Linux OpenSUSE SLES
After installed required fonts for our newly installed Win10 computer.
I found the command prompt will show some weird chars for back slash.
After done some google search and poke around, I found a solution. One of the windows fonts cause the problem
usually I could just simply delete it from font fonder..however when I was trying to delete that one.
It shows an error msg saying that font is “system protected….etc”
to delete system protected font we could simply delete the key value from Registry.
HKEY_LOCAL_MACHINE → Software → Microsoft → Windows NT → CurrentVersion → Fonts –> “(Font Name)”
in my case font name will be : msgothic.ttc, MS Gothic & MS UI Gothic & MS PGothic (TrueType)
After deleting the reg key and then restart the computer the cmd prompt is back to normal now 🙂