Switch to Admindoes not work for me - with this unticked i get a good build - tick the box and things load i get a message that it is switching to admin and the final screen is black with a mouse pointer - only way out is a resetall i have ticked is switch to admin on the build core page - i always ask - what am i missing or doing wrong
there are no new features in PE with 20H2 compared to 20H1 - other then a mess of registry errors
Quote from: adacom on November 05, 2020, 12:33:26 PMSwitch to Admindoes not work for me - with this unticked i get a good build - tick the box and things load i get a message that it is switching to admin and the final screen is black with a mouse pointer - only way out is a resetall i have ticked is switch to admin on the build core page - i always ask - what am i missing or doing wrongare we talking of 20H1 as in your previous post or 20H2 ?
Hithanks for the extra infoI never have a use for Admin, so never test for myself, not sure it helps much but I can test Win10XPE_2020-11-01 back to 19H1 18362.30 x64with basic build checked (for speed) and switch to admin on, for me it boots to a desktop with working taskbar icons (clicking yes to Admin)tested in a VM, Hopefully someone else will have a suggestion.Also, I have not had a prob with taskbar icons - assuming apps are Run From RAM checkboxed in any of the builds
this is running Win10XPE_2020-11-01 on windows 10 64bit - laptop running 2004 19041.610 - iso built and written to USB stick using rufus 3.12p
Quote from: adacom on November 05, 2020, 03:50:21 PMthis is running Win10XPE_2020-11-01 on windows 10 64bit - laptop running 2004 19041.610 - iso built and written to USB stick using rufus 3.12pI had tested "Switch to Admin" before the release and it looked good.However, I only tested it with the Techbench Original ISO 19041.508.With the last Preview 19041.610, I don't know! I have only tested the standard build, just to see and without trying to go further.If it's good for you with 20H1, keep it, without bothering with 20H2
It is not possible (or no longer possible) to Pin Applications from a Removable MediaIt is not a PinUtil limitation, it is by concept in Windows, to avoid pinning applications that might be missing.
I found a trick to bypass the Windows limitation and be able to pin Apps from the removable drive Y:\Programs
PinUtil must be launched after Explorer. To bypass Windows restrictions, use symbolic links for programs on Y: removable driveIFEX B:\,IFEX Y:\Programs\,EXEC =@%WinDir%\System32\Cmd.exe /C Mklink /D B:\Programs Y:\Programs
@ericgl Yes with also AddPin macro to Pin from symbolic links on B:\Programs. Imdisk Ramdisk is required, I had previously tried it on X: but mklink didn't work.Hoping MS doesn't change it too quickly, again and again. Silence is golden.
Good to know, is it about size > 4Gb or related to the WES8 fbwf driver ?I use the windows 10 fbwf embedded driver, limited to 4 Gb and it does not work on X: But it works fine through B: Ramdisk. It is good to be able to pin Apps again from Y: removable drive