Its a never ending battle to try and keep on top of the changes, its not like they are once every 6 months OS build update, it seems like even the monthly CU's can sneak the crApp's back on and other bits.
they are upgrading things backwards, instead of giving the user more options and customizations, they are giving you no choice, either get all or nothing like the new office setup clicktorun, you have only one button to setup and you can't choose which product you want and which one you don't, as office 2010 before windows updates in windows 7 and 8 were customizable and you can choose which updates you want, critical, important or optional, but now with windows 10 you can't have this privilege, they treat their users like they are stupid, they don't like advanced users
I try to give that choice back with MRP, well as best as i can. MRP wasn't really designed to be a tweaker so only the important ones are added or ones i get asked a lot about. I think i have the balance about right so far. I know a lot of users use the majority of the options.
its past midnight here and time to get some sleep. At least have sorted the Phone puzzler out, not quite the elegant way i would of liked but alas it a work-a-round.
but it's the oem folder that can be used to make these tweaks work after all it's all part of windows customization, oem branding, some optimizations and tweaks, right
I am avoiding Defender disabling and Windows Update tweaking within MRP options because m$ can change things every update/new build on W10. However the simple script attached (rename from txt to cmd), might be a starting point for Windows update to be set as 'Notify'. Must be run as Administrator! It covers Vista->8.1 and a section for Win10 kernels. It may or may not work on W10, probably not work on W10 Core based Editions due to the nature of those Editions. This is why i am not integrating WU stuff into MRP there are too many variables which can affect how it works. Note: As policies are used on Windows Update you will see the line about 'managed by your organization' this is normal if policies are involved. If you look at the script you can see prior to Windows 10 it was fairly simple, on W10 it has more complexity and it is forever being changed by m$ to prevent the user from changing it outside the limited options within PC Settings!
good friend only thing: at least for my humble brain I think that only end when Azure dominates entire world but for me no worries because I'm compleely envolved with open source until forget my beloved games but at least I'm NEVERMORE stay along with M$FT SHOP Bloatware trust me; I admire a lot your effort for all including me but... do you think this is valid bro??
I have been using this project since a long time and i dont even remember lol, I would lke to thank you for updating this project regularly and i am really really thankful, I have few sugesstions if you dont mind, 1. is i am using AORUS Motherboard which is gaming motherboard of GIGABYTE but when i use this project i realized that there is no banding for AORUS as itself it is another brand and product, Same as DELL has Alienware 2. My cousin is using HP OMEN Series and his laptop came with OMEN OEM windows with OMEN branding etc and i didnt see the OMEN series branding as well 3. Everything is perfect but i think the DELL Logo on username side could do better, if its in traditional state same as of HP Logo on user login screen. I am really really sorry in advance if any of my suggestion seem harsh to you. In the end i only want to make it more better and i know it has potential and little room for improvement. I hope you will put soe light on these suggestions
as i gather from your text is that Aorus is a model name for the Gigabyte motherboard? Like the GA-xxxxxx numbers.? If you have the logo's etc you can use the Custom theme set as Custom and your wallpaper(s), user logo's etc can be put into that theme folder, set config creator as Custom for the theme and MRP will do the rest to insert your own theme/brand. All info how to do that is within the readme files. Or if you wish, upload the logo's, wallpapers etc and i will put together a Custom theme for you to use with MRP. The dell logos/user.bmp is the ones i found on Dell's website. I am slowly updating certain logo's that the manufacturers have updated, it just finding the time.
For the next MRP i will be removing the Take Ownership context menu, you will still have the Command/Powershell (+admin) and Copy/Move To. The reason is because of the language problem, (that always comes back to haunt me!). So if you want to have take ownership you will need to use the script within the 'Optional/Misc_ExtraScripts' folder this has REMarks in the script to show you how to alter the "Take Ownership" wording to your own native language by simply editing a variable's parameter. To create a script with a language detection and change would not be an easy task so sadly i have removed it from MRP's option.
This is the script for TakeOwnership you can see where the variable is to be changed for your native language. You have to save with Unicode to allow some languages. The *S-1-5-32-544 is language independent (so m$ says as the * tells the registry to not change to English), this is for the word Administrators. I may have some of the wording slightly wrong for 'Take Ownership' as I used Google Translate for the examples. Spoiler: Takeownership - Script Code: @echo off CLS color 1f TITLE Checking for Admin... echo. cd %systemroot%\system32 call :IsAdmin TITLE TakeOwnership Context Menu cls color 1f echo. REM Variable Admin = Administrators Group, you could have the username, or Administrators spelt in your language. REM However *S-1-5-32-544 is language independent for Administators. SET "Admin=*S-1-5-32-544" REM Change the CTMenuName variable's 'Take Ownership' wording to your native language. Such as... REM Dutch -----------> SET "CTMenuName=Neem Eigendom Over" REM French ----------> SET "CTMenuName=Prendre possession" REM German ----------> SET "CTMenuName=In Besitz nehmen" REM Spanish ---------> SET "CTMenuName=Tomar posesión" REM Portuguese ------> SET "CTMenuName=Tomar posse" SET "CTMenuName=Take Ownership" REM Take Ownership Context Menu Reg delete "HKCR\*\shell\runas" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas" /ve /t REG_SZ /d "%CTMenuName%" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas" /v "HasLUAShield" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas" /v "NoWorkingDirectory" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas" /v "Position" /t REG_SZ /d "middle" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas\command" /ve /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" && icacls \"%%1\" /grant %Admin%:F /c /l" /f >NUL 2>&1 Reg add "HKCR\*\shell\runas\command" /v "IsolatedCommand" /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" && icacls \"%%1\" /grant %Admin%:F /c /l" /f >NUL 2>&1 Reg delete "HKCR\Directory\shell\runas" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas" /ve /t REG_SZ /d "%CTMenuName%" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas" /v "AppliesTo" /t REG_SZ /d "NOT (System.ItemPathDisplay:=\"C:\Users\" OR System.ItemPathDisplay:=\"C:\ProgramData\" OR System.ItemPathDisplay:=\"C:\Windows\" OR System.ItemPathDisplay:=\"C:\Windows\System32\" OR System.ItemPathDisplay:=\"C:\Program Files\" OR System.ItemPathDisplay:=\"C:\Program Files (x86)\")" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas" /v "HasLUAShield" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas" /v "NoWorkingDirectory" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas" /v "Position" /t REG_SZ /d "middle" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas\command" /ve /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" /r /d o && icacls \"%%1\" /grant %Admin%:F /t /c /l /q" /f >NUL 2>&1 Reg add "HKCR\Directory\shell\runas\command" /v "IsolatedCommand" /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" /r /d o && icacls \"%%1\" /grant %Admin%:F /t /c /l /q" /f >NUL 2>&1 Reg delete "HKCR\dllfile\shell\runas" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas" /ve /t REG_SZ /d "%CTMenuName%" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas" /v "HasLUAShield" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas" /v "NoWorkingDirectory" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas" /v "Position" /t REG_SZ /d "middle" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas\command" /ve /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" && icacls \"%%1\" /grant %Admin%:F /c /l" /f >NUL 2>&1 Reg add "HKCR\dllfile\shell\runas\command" /v "IsolatedCommand" /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" && icacls \"%%1\" /grant %Admin%:F /c /l" /f >NUL 2>&1 Reg delete "HKCR\Drive\shell\runas" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas" /ve /t REG_SZ /d "%CTMenuName%" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas" /v "AppliesTo" /t REG_SZ /d "NOT C:" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas" /v "HasLUAShield" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas" /v "NoWorkingDirectory" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas" /v "Position" /t REG_SZ /d "middle" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas\command" /ve /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" /r /d o && icacls \"%%1\" /grant %Admin%:F /t /c /l /q" /f >NUL 2>&1 Reg add "HKCR\Drive\shell\runas\command" /v "IsolatedCommand" /t REG_SZ /d "cmd.exe /c takeown /f \"%%1\" /r /d o && icacls \"%%1\" /grant %Admin%:F /t /c /l /q" /f >NUL 2>&1 Reg delete "HKCR\exefile\shell\runas" /f >NUL 2>&1 Reg add "HKCR\exefile\shell\runas" /v "HasLUAShield" /t REG_SZ /d "" /f >NUL 2>&1 Reg add "HKCR\exefile\shell\runas\command" /ve /t REG_SZ /d "\"%%1\" %%*" /f >NUL 2>&1 Reg add "HKCR\exefile\shell\runas\command" /v "IsolatedCommand" /t REG_SZ /d "\"%%1\" %%*" /f >NUL 2>&1 echo. echo Done. echo. Pause exit ===================================================================================== :IsAdmin Reg query "HKU\S-1-5-19\Environment" If Not %ERRORLEVEL% EQU 0 ( Cls & echo. & Echo You must have administrator rights to continue ... & echo. Pause & Exit ) Cls goto :eof Adjust wording as you wish. I cannot guarantee it will work for all languages, you will have to test on a VM/Test PC. There are alternative scripts/registry files on the internet for the Take Ownership context menu that may be in your native language.
If option left un-ticked (No) Code: # ################################################################################################################################# # Secure UAC Desktop Dimming # If set to Yes will prevent the UAC from dimming the desktop, it does not alter anything else with UAC. # Default is No to allow desktop dimming,{OS Default}. :DisableSecureDesktopDim=No # #################################################################################################################################
Actually AORUS is the brand or series of Gaming Edition of All Gigabyte products, Same as Alienware is brand of DELL related to gaming, And i have created the file for AORUS Gaming and i would like to share it with you and want you to test it for me and let me know if there are any issues or it would be great if you could fix them aswell xD And as for OMEN series of HP ( Which is same Like Alienware of DELL) I can share with you OMEN series Branding as well, if you will not mind
Looks like you have created a 'brand' for it saves me a job I did find a wallpaper but it was 8mb and 4K resolution, looked awesome but i tried to get the file size down to 250kb but it looked awful. Now if you could run the QTool and post the results for the AORUS board i can see if it is possible to utilize that brand folder in MRP, if the DMI area still shows Gigabyte and nothing about Aorus in that area then i am afraid i cannot add that brand as MRP looks at the DMI area for automatic branding, then SLIC, then MSDM (if the latter two are present). The only area that is of interest is the middle section of the QT's report the area that shows the DMI - no keys will be saved to the report so it is safe to post. But it can be made to be a Custom brand which you can set so that for that Mboard the ISO/USB will always brand your custom theme. To set as Custom all you would need to do is rename the AORUS bit to Custom such as Custom.theme, Custom.reg basically any filename with AORUS to Custom, copy the files into the OEM's.7z's Custom folder overwriting the files within that then set mrpconfig.ini's :CustomTheme=Custom , this will tell MRP to use that theme/branding and ignore any Gigabyte references. MRP's log will still mention that Gigabyte is detected in the DMI but will ignore that and use your theme. The OMEN brand if done same way would also brand that other computer as above but ignore the HP dmi and use the OMEN branding within Custom folder. Attached is the wallpaper i found (compressed to 1920x1080 and below 250kb) at full 4k resolution it looks stunning!