@AeonX I stocked up on H310C boards and Pentiums so im set with 7 for as long as that lot keep working. I havnt tested the biostar igpu driver on 8.1 yet, i will do at some point. I got used to the flat metro ui on 8.1 and 10. I can be windows 10 free for quite a long time.
The biggest problem with 7 that I realize is if browsers stop supporting it and browser updates are the only ones that I particularly consider indispensable. The rest of the programs mostly continued to work except those developed by Microsoft and that is what matters. It was the best OS Microsoft could make and that time was the pinnacle of its existence. Microsoft striving to make the most efficient software possible, it was truly a golden age for Windows. With 8.1 there were really significant improvements in several ways however the design proposed by microsoft was not the best and turned out not to be a very popular OS.
The browser and security sides arent an issue because i got debian. The stuff i use regularly is old and hasnt been updated in years and works on 7 8.1 and ltsc. IM still using the old wav, vob, ac3 and mp3 formats ive been using for years. The only thing that has changed is i now use vm's on occasion so i upgraded to 8gb ram, everything else is the same. If needs must i can go back to 8.1.
She has 3 sons who are avid gamers, a lot of house work to do and 10 computers to maintain. Spare time is hard to find I'm not a trusting person. Perhaps I believe too much of the negativity I read all over the place. I won't do ANYTHING online unless it's through a VPN. In 2017 Australia introduced it's own mass surveillance laws, much like the stuff Ed Snowden disclosed. I don't believe any one should have access to any of my personal information. I won't even give people my cell phone number. Blizzard is no more trustworthy than steam Epic or Origin, so if they want to look at what's on my systems, all they should see on a VM is nothing. There's nothing on the VM except the battle.net client and Hearthstone. There isn't even a browser installed. I struggled for two years with the move to Windows 10 until I found MSMG Toolkit. Windows 10 (IMHO), is also a UX disaster. I hate tiles.So with Open shell and several other tweaks I was able to make Windows 10 bearable to look at, and MSMG took care of the rest. So I took the plunge. But I will always be overly paranoid with security and I don't miss the technologies I'm blocking. I have no interest in "a connected world". I'm too old fashioned. Lol. Other way around. The CIA and KGB are watching everyone here
So I used the MSMG toolkit to remove Edge from and ISO (Windows 10 1903). It worked and it was gone but after running an optional update it reinstalled Edge. Has anyone else noticed this?
I agree however it is a bit more digestible than that of 8.1 But the worst thing about Windows 10 for me is not the design of its UI but the weight of the UI on OS which in my opinion got a lot heavier than 7 and 8.1 and many other things that weigh the OS unnecessarily.
Readme.txt Known Issues: ============= - Using ToolKit with Antivirus Programs enabled can affect the ToolKit's operations. - ToolKit's ToolKitHelper.exe may be flagged as a Virus/Trojan/Malware Program, Don't worry it's just a False Positive Sign. - The ToolKit won't support Post-Servicing of ToolKit serviced source images with other similar tools. - Windows 8.1 - Default Metro Apps Pack missing Office OneNote Appx file. - Windows 8.1 - Integrating Windows Remote Server Administration Tool (RSAT) along with other features will break the Integration with an error code 0x80092004. - Windows 7/8.1/10 v1507/v1511/v1607/v1703/v1709/v1803 Component removal has been removed temporarily. - Windows 10 v1809 - Integrating or Installing Windows Updates after the component removal can restore removed components empty resources files/folders. - Windows 10 v1903 - Integrating or Installing Windows Updates after the component removal will restore the removed components and this is due to the recent change in Microsoft Updates mechanism. - Windows 10 v1703/v1709/v1803/v1809/v1903 - Custom User Account Picture Integration is not working in Logon Screen although it's been displayed in Start Menu User Icon. - Windows 10 v1809/v1903 - Windows Media Player/PhotoViewer/Win32Calc Skins features are not working. - Windows 10 v1709/v1803/v1809/v1903 - It has been reported that in the Format USB Function, the Diskpart command "list" is not working when used within the Script.
What with tv's fridges alexa etc Orwell would be pissing himself. One machine ONLY connected to the world wide wait is enough.
Best i could manage on LTSC(with my work alone) is around 8000 handles, 7 is about 5000 but not tweaked as much.
Ok I have tested the 1903/1909 with latest CU and have added automatic methods to detect and remove the possible changes the next CU will be making to the current state. Only upcoming more CU's can decide the fate of the component removal to support images with updates integrated as making modification for each CU is difficult.
My order for Windows 10 v1903-1909 x64 en-us: ===================================== [1] - Select the Source Images using [Source->Select Source from Source <DVD> Folder] menu (18362.30 or 18363.418). [2] - Integrate the required Windows Features (Except Microsoft .NET Framework 3.5) using [Integrate->Windows Features] menu. [3] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [4] - Integrate Windows Updates using [Integrate->Windows Updates->Windows Updates] menu (.DotnetCU+Flash+SS+CU). [5] - Integrate the required Windows Custom Features using [Integrate->Windows Custom Features] menu. [6] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [7] - Integrate Microsoft .NET Framework 3.5 Feature using [Integrate->Windows Features->Microsoft .NET Framework 3.5) menu. [8] - Integrate CU again. [9] - Remove all required Windows Components using [Remove->Remove Windows Components] menu. [10] - Customize the Image using [Customize] menu. [11] - Apply & Save Changes to Source Images using [Apply->Apply & Save Changes to Source Images] menu. [12] - Re-Build Source Images using [Apply->Re-Build Source Images] menu. [13] - Convert .WIM to .ESD. [14] - Create ISO.
@MSMG And the integration of this reg file does not work. This one works, but only if integrated through the command line, as I did before.
This is the tweak you want to include isn't it. Code: ; Configure Windows 10 File Explorer to Open This PC Instead Of Quick Access [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "LaunchTo"=dword:00000001 If you want to integrate it through command-line then Code: [HKEY_LOCAL_MACHINE\TK_NTUSER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "LaunchTo"=dword:00000001
@MSMG Add this fix to disable Feedback Frequency if Insider Hub is deleted. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "ManagePreviewBuilds"=dword:00000001 "ManagePreviewBuildsPolicyValue"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Siuf\Rules] "NumberOfSIUFInPeriod"=dword:00000000
The first two tweaks are related to disabling Insiders Build and these will be of no use when the entire Insiders Build option is removed. The third tweaks is related to Privacy option and applying it didn't entirely disable choosing the frequency.