Well, the system I'm talking about was NEVER upgraded by the ISOs created by any converter, ABBODY or ADGUARD. Thus an items in my menu have appeared nor from the ISO but as a result of the executing of some utility which knows how to add or replace Power plans. Seems that an API exists which permits to make it. P.S: I've succeed to find in saved HKLM of 17025, SYSTEM\ControlSet001\Control\Power\User\PowerSchemes\, those damn russian strings and thus can delete them and HOPE that a next upgrade will restore standard values.
I think it's bug in windows and bug not all of the users have it. I did upgrade from 17133 to 17639. I hope it work in 17650.
My laptop's secure boot was already disabled but still couldn't install this build. I was even able to install 17639 but not 17643 and 17650. I'm still having a hard time updating to 17650.
Code: ============================================================ UUP directory contains multiple editions files: ============================================================ 1. Windows 10 Home (x64 / en-US) 2. Windows 10 Pro (x64 / en-US) 3. Windows 10 Lean (x64 / en-US) 4. Windows 10 Home N (x64 / en-US) 5. Windows 10 Pro N (x64 / en-US) ============================================================ Enter edition number to create, or zero '0' to create AIO ============================================================ > Enter your option and press "Enter":
I successfully install build 17650 on old pc (11 years old). I couldn't install this build on new laptop (4 month). Only builds 17133/4. Is it not weird ?
It happens: new hardware support codes takes at least a year to became as stable as stable edition of the Windows. My practice is likewise: my old Thinkpad R500 issued in 2009 practically haven't problems since 9841 till 17650 but at less then one year old Thinkpad P51 I have in some builds GSODs during upgrade due to incompatibility of the fingerprint scanner driver those builds installed. Had to delete this device for some builds ( seems three early 17xxx ).
Another weird thing happened. I tried clean installing 16299 twice and updating via Windows Update to this build but ran into many errors both times. After that I tried clean installing this build via USB drive and viola! It installed!
There is big difference between WU and clean install. I tried clean install, upgrade and install on VHD, and it fail on these three methods.
yea i just made rs4 and rs5 ISOs lol creating boot.wim and install.wim took the juice out of the CPU Unfortunately i have i7 with only 4 hardware threads in total else more juice would have been extracted , rofl.
CloudE is a weird SKU. Does not seem to belong to Core or Professional but to independence. In addition, I found that the maximum memory limit is 4GB? Code: <sl:policyInt name="Kernel-WindowsMaxMemAllowedArm">4096</sl:policyInt> <sl:policyInt name="Kernel-WindowsMaxMemAllowedArm64">4096</sl:policyInt> <sl:policyInt name="Kernel-WindowsMaxMemAllowedx64">4096</sl:policyInt> <sl:policyInt name="Kernel-WindowsMaxMemAllowedx86">4096</sl:policyInt>