Resolved.. did a system reset, installed all (one at a time, testing between each) but 2 of my programs, then did a Macium Backup of the system.
So far, the speed and performance has been returned. I think the problem was a corrupt file/program. If it turns out to be AlZip, that should also eliminate Explorer crashing intermittently. Time for a new archive program. Strange thing is, it also affected my NIC, making that piece of hardware crash at times.
Just disabled sets. Found it spooky with progs like Libreoffice opening in a tab then finding adding another tab ran up Edge that I don't use.
Maybe one day but not now!
I was surprised when, after I figured out the proper triple boot setup, that
1) The ISO I created did not boot to the Windows 10 Install but instead to the Language selection screen, and the rescue environment and
2) (No doubt many of you will cheer), Wzor Combined 17666 ISO direct link returned 404 The day before the ISO was available.
Anyway the 17661 ISO was installable so I intalled that and ran setup.exe from the 17666 ISO saving nothing and 17666 was now installed in its own partition (I had backed and reinstalled Windows Server 2019 removing Windows 10 from the boot menu).
Who thinks Microsoft will ever explain why it releases ISO's that are not bootable and surpresses any that are bootable.
Mushrooms - rise up
In this build Microsoft added an option to show or not the accent color on the borders of the windows, if that option is enabled, that pixel in the edge of the windows will be seen with the accent color:
But if one or more tabs only from UWP apps are open, that pixel retains the accent color at the top of the title bar:
If you mix those UWP apps tabs with one or more tabs of the file explorer, that pixel doesn't appear with the accent color at the top of the title bar:
That option is found in Settings-Personalization-Colors-Show accent color on the following surfaces, in previous builds the second option only said "Title bars", in this build they added "and window borders".
Education edition is almost identical to Enterprise, but there are a few features missing since 1709.
Pro Education is the same but does not have Cortana, Spotlight and Windows Store suggestions. It is also possible to setup a computer with specific settings setup by the educational institution, by using an usb thumbdrive with all the settings.
MS have not released any isos. The problem is we (including WOZR) are making them using unofficial methods, and using unofficial tools for making them, and if MS change something the unofficial tools do not always work and need to be updated.I was surprised when, after I figured out the proper triple boot setup, that
1) The ISO I created did not boot to the Windows 10 Install but instead to the Language selection screen, and the rescue environment and
2) (No doubt many of you will cheer), Wzor Combined 17666 ISO direct link returned 404 The day before the ISO was available.
Anyway the 17661 ISO was installable so I intalled that and ran setup.exe from the 17666 ISO saving nothing and 17666 was now installed in its own partition (I had backed and reinstalled Windows Server 2019 removing Windows 10 from the boot menu).
Who thinks Microsoft will ever explain why it releases ISO's that are not bootable and surpresses any that are bootable.
Mushrooms - rise up
We have seen that issue before.
At first screen, press shift+F10, navigate to root drive of installer and run setup.exe
Another way round it is to use @Karis dism method to clean install.
I am seeing a lot of complaints from users on other sites from users who are upgrading to 17666 for first time just to get dark theme or sets. The conplaints are various but the common theme is "screw MS as my pc is broken now".
Of course, us seasoned Insiders know Insider builds can be flakey at times.
Somehow MS is not getting it over clearly the risk to users of using Insider versions.
Quote
