I opened cmd prompt, typed Explorer C: which usually opens the C drive, it flashed a explorer window then instantly closed it...
Well something interesting.... I went into registry and made sure that HKLM/HKCU >>> explorer>separateprocess is set as 0 then restarted pc, now if i click ThisPC or any folder it closes and restarts explorer.exe but still no opening of any folder
Cant even test network drives either as cant see the windows to access them Think this insider 'canary' build has sung its last song
On my test laptop 25346.1001 now went thru after the app removal, "apply photoviewer....." now it is scrolling thru all other settings Explorer doesn't work, the desktop and taskbar disappear for a second and reappear but no explorer is opening.
I really have no idea which option or removed app is causing it.. Everything works on any other w1x build apart from this canary one.
what is PowerAutomateDesktop_8wekyb3d8bbwe ?? i know that gets removed as it not in the exclude apps for insider as it never existed before did it? i cant remember seeing it... ''Power Automate enables you to trigger your desktop flows from cloud flows. To take advantage of this feature, you need to install an on-premises data gateway on your device.'' Still none the wiser.
just tweaked the safe apps removal to exclude some of the new apps i have noticed that wasn't in the previous exclusion list... Doubt it make any difference but worth a shot. This is my last test install for today as it soon my watch adverts i mean television time
Well i have tested many things today with the canary insider and nothing seems to fix that explorer weirdness.
Interesting... using no config file and just the standard decompile, oobe.cmd and oem's.7z files on this canary build it aborts MRP part way through so it never brands... Yet file explorer works!! It is apparently a now unsupported registry entry -- Now which one
Just debugging why no branding when no options used or no ini file... Not just for Insider builds as it may happen on normal ones too... Added more entries to the earlyrun log... I know the 'error', if any, is between lines 0103 and 9705 But think i may continue tomorrow after this install test as i need a break
Canary build are buggy builds Do test on buggy builds.. no make any sense Who knows what they will next in such builds?
Trouble is these instabilities may end up in a later CU or Build! So i am trying to mitigate them early on.
Hopefully fixed the issue when no ini file is present, it just should now skip all the options and starts checking the DMI etc to find any brand names and SLIC/MSDM etc -- just like how the original project began... This particular fix is critical regardless if Insider or normal install. My last install for the night with this updated check and skip...
Well it appears to be W11 MRP is being run as normal but then the 'untouched' W11 setup just deletes MRP files - i bet it was that bastard Defender
I am sure it was defender sneakily nabbing files because the scripts folder is still there but the important mrp files are not and when i looked in defenders 'history' there is no trace of any deleted, cleaned or quarantined files... and i can just imagine defender having this look on its face --> Well enough for today, will continue again tomorrow
I wonder how you are able to debug 10+ lines of code ... let alone find a buggy registry key in all this mass this is a talent ...
Well in total the first part of MRP which is the branding and option setting etc is 21,460 lines. Addon Manager (2nd part you normally see with desktop behind) is around 10,900 lines now. It takes a bit of debugging at times, i just add 'goto :blahblah' parts to skip sections and have a lot of echo lines going to a log so i can see roughly where what script is at... Not talent, just pure shear determination that m$ wont beat me...
I cant release MRP 151 in this state as i have to get this branding part at least in a stable state even if no options ini used. If i worked for m$ and was this checking etc i would be fired by now