Anyway this 17133 build has many strange things. This is what I've found. 1) Transparency on taskbar does not work like 1709 (Redstone 3), that is if I put a full screen image as background image, taskbar change its coulour but I can't see the background image in transparency, like on 1709. 2) Installing .NET Frameworks from the Control Panel -> Adding Windows functionalities, always fails. The only valid workaround is to open an elevated command prompt and use DISM.EXE from the homemade ISO. 3) Installing Office 2016 make all relative icons (Word, Excel, PowerPoint, Access, and so on) with the default blue background color, instead of the right one (Excel is green, PowerPoint is orange for example). 4) The Security screen which should allow to disable the realtime protection, when launched for the first time after a reboot seems to search for something (it requires 1-2 mins), while on 1709 opens instantly. If this is an RTM I'm wondering how and what Insiders tested and how and why Microsoft didn't fix these issues !!!! I'm not the only one experiencing such behaviour and I'm very disappointed about this.
It is absolutely normal, that you cannot install the .NET Framework 3.0 for a not yet officially released OS RTM variant via Windows Update. As soon as the RTM variant is out, Windows Update will support the installation.
Maybe he can put all sku's in? btw, dism puts in the key by itself now, only not the gVLK but the oem:nonslp key, the one needed for the HWID.
If you should mean me, I always do it by using the command Code: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:X:\sources\sxs where "X" is the letter of the USB Flash Drive with the OS Image on it.
Hello everyone, How can i download Enteprise version via UUP? And i want to use EI.CFG similar to this to show all editions on x64 image. I suppose image should be CPBA and not CPRA for this to work. But i couldn't find CPBA build on UUP adguard. Code: [Channel] volume [VL] 1
Win 10 iso's don't need an ei,cfg like 8.x iso's to show all editions, it shows all editions by default after using the "i don't have a key" option during initial setup. Only with UUP converted iso's you need to create the other sku's yourself by offline set-edition them. And when you have a bios MSDM you can use this ei.cfg* to skip the sku autoselection based on the MSDM. *) ei.cfg Code: [Channel] _Default [VL] 0
after alll, the forum has proven to be good, issue is solved, even you tried to help (to reproduce the issue, you will need cs-cz or pl-pl as host OS though) ) I like gVLK key because of MS Toolkit (it even works on arm64 nicely). And yep, the improvement for uup converter to produce "virtualized editions" in general too will be most wanted. )
What i said about the key, dism set-edition will put in the oem:nslp key bey itself (when target is enterprise), it does it from 17063, iirc.. MTK or any proper KMS tool will always put in the gVLK by itself. But the need for KMS activation is practically gone since all sku's can have HWID