I not see anything in that unattended XML that could cause those issues. Side note: Any reg entry/tweak that has a 'policy' type edit will usually trigger the banner 'Some of these settings are hidden or managed by your organization'.
Just a heads up on progress for the next Project release, (v136 scheduled for release early April 2021)... Options that are now added: General: 1} Use 'Full windows drag' - Show contents while dragging and not just the outer framework. 2} Ignore 'Model Name' - ideal for cloner's to prevent 'Model Name' conflicts when restoring the image to other hardware. Using this option will override and not use any DMI/BasePro data or user entered naming. W10 Only: 1} Use File Explorer's classic 'Compact' spacing mode for 21337 and later. W10-Apps: 2} Added 'Screen Snip' to the internal list of not to remove apps. Other Internals: 1} Fixed Release ID to show 20H1, 20H2 etc correctly. 2} Adjusted code to show all info screens regardless if Silent mode used when installing any Server OS's. 3} Clean-Up module will now always show, it is only shown for a few seconds, this prevents some errors occurring when it was run 'silent' before. 4} Various updates to log entries (spelling etc) There may be other items to add to the list and they will be shown in the Change Log/Summary when released. A total of about 216 various options, and all are up to the end user to decide to use any or none.
Will fix the MRP log entry for the 'installation type' to just say 'Server' , missed that one! Hopefully i will get a bit of time to work on coding this week.
Have made time this morning to address the issue of the 'OS Installation Type' above and also separate the 'Release ID' and 'Display Version' data. So you may see 2004/2009 for 'Release ID' and 20H1/20H2 for the 'Display Version' , it all depends if the data is present, if it is, then it is shown on their own lines respectively. Note: The 'Display Version' seems to be only on the newer W10 OS's, also sometimes in the Insider/Preview channels it may say info such as 'Dev' (Developer) etc instead. example QT (Snippet): Code: Release Identifier : 2009 Short Display Version : 20H2 This should also be shown in the same way on MRP v136 and later.
MRP v136 is now at the Release Candidate {RC1} stage. On target for early April release. The new Options are finalized, basically its cosmetic bits and pieces to finish off as and when i get time. Done a few internal code tweaks and also added some extra info lines to the 'Add-On Manager' screen, if the 'Silent Mode' is not used, to show the project's processing progress.
in WinTel.cmd %REGEXE% is used in lines 374-376 and 500-501 but never being set or do I miss something?
A copy/paste mistake on my side Easy to fix either change %regexe% entries to just REG or set the variable at top of script under the echo off line.
Have uploaded a new WinTel zip 2nd post download link, password and hashes updated. Borrowed a laptop, downloaded the old WinTel file , fixed the bits required and also done a few small updates to the code, just some new remarks and uploaded the new zipped file. Not seen anything else wrong so fingers crossed all sorted for the time being.
Thanks a lot for this beautiuful job . Route M$ IP's from Wintel Script Copied to my Win10 OEM Pack Setupcomplete Script i was not aware of Route Tool. Thanks a lot again
The route command is quite useful as it saves messing with the hosts file which w10 not really take any notice off now. In wintel i remarked those m$ route addresses to allow msn, hotmail and certain m$ sites to work. There is a lot more that can be added and i just used a few.
Quick heads up about the Project's progress... The next Query Tool v41.0 is at RC1 stage and a little addition done today. Code: Media Installation Method : Upgrade OR Code: Media Installation Method : Clean Clean = Fresh install , not a upgrade/repair. Upgrade = Upgraded install which could be from a previous OS ie 7, or a Win 10 Build to Build {for example Insider to a later Insider}, even a repair installation 'over the top' could trigger this. At some time in the future i may add extra information about the 'Upgrade' part such as what OS or Build it was previously upgraded from, but as that data can get quite extensive it may be limited to just one or two Builds etc... Fixed a issue that sometimes the 'VL/KMS Capable/Permitted' result was set as 'No' when it should of been 'Yes. ------------------------MRP v136 is at RC2 stage also.