its all down to timing, mrp takes a bit of time to complete, during that time office gets its updates - if device connected to net, so files change etc , so your office version changes.
i don't have the office in the oem folder the image is syspreped. It doesn't matter either, I've just left out MRP. Thank you anyway
As can be seen i have already started on the next release , nothing to report at this moment as time and weather been against me so not been able to work on the project for a few days.
Just added four new 'General OS' options (Advanced) 1. Add 'Run as administrator' right-click C/Text menu entry for .vbs scripts. 2. Add 'Run as administrator' right-click C/Text menu entry for .js scripts. 3. Add Install {Register} and Uninstall {Unregister} DLL files on C/Text Menus. 4. Add Install {Register} and Uninstall {Unregister} OCX files on C/Text Menus. The above should hopefully be OS Translated if possible, if that fails then they will be in US-English by default. Could not find any look up table for Register/Unregister so used Install/Uninstall respectively. Set as 'Advanced' as not everyone will need those options.
.Ocx works too but it is less used, but added as there can be the odd time it is needed. The run as admin for .vb script files is quite useful, was one of my personal tweaks that i decided to add into mrp.
I just renamed a txt file as ocx to test , it caused a error but i expected it as it was a non ocx file My vbs scripts are usually needed to be run as admin, just saves me a lot of time.
Just nipped on while on my break to mention that another option for w10 is being tested/in progress. First attempt partly worked, however the new code routine seems to set it this time, but due its nature the os may not always allow it, it should also work on core editions. More details later once more tests done. EDIT: Sadly core/home editions the routine seems not to work, must be hardcoded in the os kernel that prevents any adjustments. The option does appear work on older os's and w10 pro and above.
The option was to prevent hardware device drivers from being forcefully downloaded/installed on w10 Home/Core Editions, but m$ have hard coded it to just get them regardless of the user's wishes. - i tried several ways, all failed on Core - works ok for w10 Pro and above, also for Vista/7/8.x kernels. So have re-edited and added that as a advanced General OS option on the [Extras] tab, this sets the hardware device drivers setting to Off/No which seems to be respected for w10 Pro and above and Vista/7/8.x kernels, note that this does not use any policy edits and so is easy reversible via the OS's 'System Properties --> Hardware --> Device Installation Settings' GUI. It will be auto disabled on w10 when using the other 'Disable Driver Searching' option as it is part of that routine, less the policy parts, also on any w10 Core/Home Edition it will be auto disabled. I have hardened the 'Disable Driver Searching' routine and it should prevent ANY drivers, but there may be some specific ones such as for 'Graphics Cards' because those *may* get force downloaded/installed by m$ design. This is why there are two similar options, the one on the Extra's tab is for all supported OS's/Editions and does not involve any policy edits which can cause a few headaches when reversing the changes! A side note that on w10 Core/Home using the set Metered option does at least slow down the flood of driver updates, not fully prevent them. The Metered option is set for Wi-Fi, LAN and mobile data too! If you wish to prevent/control WU downloads/drivers, there are other MDL applications that can help... Such as Sledgehammer , WUMT etc. MRP v135 is at TC8 stage and is now progressing nicely -- after a few early crashes when those extra or missing pesky missing " {quote marks} glitches was sneaking in the code.
Had a bit of spare time and so worked on the MRP Branding tool this morning -- (now at v2.4) It is quite stable and no reports of weird effects or crashes. I will most likely release this one soon as i know a few would like to test this out. Some Server OS's are not supported due to the nature of how they react to being messed about with. There may be the odd bug i have overlooked but they should not cause any major problems.
Just a heads up as I been busy for a few days with work, MRP is still progressing and is at TC10 stage now... Testing something new - once it is known working and no problems or any adjustments required to make it function with no side effects then i will mention what it is, i know it could be useful to quite a few users of MRP.