Not needed, you can longterm KMS or just standard KMS activate it, for plain kms activation use KMS_VL_ALL v26 by @abbodi1406
@Leope So for the Settings windows, the programmer uses the blue as paint color instead of the erase instruction (white). The flash is attenuated. and some will not notice it. Microsft can easily correct the bug.I hope that the insiders reported this problem. It is cosmetic but annoying.
This will please you and everyone who has that bug, build 18262: As it happened with the fix of the bug of the task manager arrows, this will soon arrive at build 17763.
To investigate more in depth, I need the pdb file for explorer.exe or the source (proprietary) Reversing and debugging with Ida Pro will take from my time. Not worth it
I just tested windows server 2019 for brightness test on: Acer 1810TZ (Intergrated intel graphics) HP 8460p (AMD graphics) none of them have any bugs with brightness on reset.
Well, new cu so new update experience with ISO 1809.104. This time it did crash with error "0xc1900101-0x30018. Could just have a quick look at the screen before it rebooted and reverted to 1803. The criminal in this case seemed to be the 'wpprecorder.sys'. Travelled around the net and did the following: "fsutil behavior set DisableCompression 1" "command prompt and c:\windows\system32\ compact /u drivers\*,sys" Another try with update and this time it finished with success. But it still is not possible to install 1809 on an external USB HDD. It crashes during the first boot, and eventually ends up with an "inaccessible boot device" and boots however only to safe mode. I would say that MS this time has messed up so many things that even they don't know how and when they'll fix them. It certainly should not be called October 2018 update, but maybe Christmas 2018 update if it ever will be ready then.
Finally upgraded from 17134.xxx to 17763.17 by WU, all went well, this time no userfiles deleted Now clean installing it, using MRP by @mxman2k
Yes but the process is not extremely simple. You have to use dism /add-package to integrate updates to boot.wim install.win and winre.wim indices From the boot.wim index 2 you can also get updated bootloader and setup files for install media. This involves mounting the original (not the updated as previously described) boot.wim index 2 one more time, integrating the WinPE Setup-Client and Setup-Legacy cab files found in PE ADK for 1809, applying the CU to image and then copying ONLY ANY UPDATED files to the installation disk. Check \Windows\Boot\PCAT, Windows\Boot\EFI, \sources folders inside the mounted boot.win index 2 for UPDATED files - sorting by date will help because you know when you applied the CU. Replace only files on installation media with the updated ones. With this complex method I have created install media for the latest CU: boot.wim winre.win are also updated AND bootmgr, appraiser.SDB and some other setup files have been updated on the installation media.