From 71d613b49d278fa0dc50d72e3d18858e051b748f Mon Sep 17 00:00:00 2001
From: <>
Date: Mon, 19 Aug 2024 19:21:42 +0000
Subject: [PATCH] Deployed 2748767 with MkDocs version: 1.6.0
---
search/search_index.json | 2 +-
sitemap.xml.gz | Bin 127 -> 127 bytes
userguide/index.html | 4 ++--
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/search/search_index.json b/search/search_index.json
index 248ec260..e3aa46cf 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to the WinUtil Documentation!","text":"
Welcome to the official documentation for WinUtil, your go-to utility for optimizing and managing your Windows environment. Whether you\u2019re an IT professional, power user, or regular user, WinUtil provides a comprehensive set of tools to enhance your Windows experience.
"},{"location":"#running-the-latest-release-of-winutil","title":"Running the latest release of WinUtil","text":"
You will first need to start a Powershell terminal as Admin.
Now you can run the following command:
irm christitus.com/win | iex\n
Info
WinUtil is updated weekly as of the time of writing. Consequently, features and functionalities may evolve, and the documentation may not always reflect the most current images or information.
Windows Security (formerly Defender) and other anti-virus software are known to block the script. The script gets flagged due to the fact that it requires administrator privileges & makes drastic system changes.
If possible: Allow script in Anti-Virus software settings.
If you are having TLS 1.2 issues, or are having trouble resolving christitus.com/win then run with the following command:
If you are unable to resolve christitus.com/win and are getting errors launching the tool, it might be due to India blocking GitHub's content domain and preventing downloads.
#69 Turn on fast startup: Press Windows key + R, then type:
control /name Microsoft.PowerOptions /page pageGlobalSettings\n
If that doesn't work, Disable Hibernation: Press Windows Key+X and select 'PowerShell (Admin)' (Windows 10) or 'Windows Terminal (Admin)' (Windows 11) and enter:
powercfg /H off\n
#69 95 #232 Windows Search does not work: Enable Background Apps
#198 Xbox Game Bar Activation Broken: Set the Xbox Accessory Management Service to Automatic
Open the generated HTML report to identify energy consumption patterns.
Review Event Viewer:
Open Event Viewer by searching for it in the Start menu.
Navigate to \"Windows Logs\" > \"System.\"
Look for events with the source \"Power-Troubleshooter\" to identify power-related events.
Check Wake-up Sources:
Open a Command Prompt as an administrator.
Use the command powercfg /requests to identify processes preventing sleep.
Check Task Scheduler for tasks waking up the computer.
Use the command powercfg /waketimers to view active wake timers.
Resource Monitor:
Open Resource Monitor from the Start menu.
Navigate to the \"CPU\" tab and identify processes with high CPU usage.
Windows Settings - Activity History:
In \"Settings,\" go to \"Privacy\" > \"Activity history.\"
Turn off \"Let Windows collect my activities from this PC.\"
Network Adapters:
Open Device Manager by searching for it in the Start menu.
Locate your network adapter, right-click, and go to \"Properties.\"
Under the \"Power Management\" tab, uncheck the option that allows the device to wake the computer.
Review Installed Applications:
Manually review installed applications by searching for \"Add or remove programs\" in the Start menu.
Check settings/preferences of individual applications for power-related options.
Uninstall unnecessary or problematic software.
By following these detailed instructions, you should be able to thoroughly diagnose and address battery drain issues on your Windows laptop. Adjust settings as needed to optimize power management and improve battery life.
"},{"location":"KnownIssues/#troubleshoot-errors-during-microwin-usage","title":"Troubleshoot errors during Microwin usage","text":""},{"location":"KnownIssues/#error-0x80041031","title":"Error 0x80041031","text":"
This error code typically indicates an issue related to Windows Management Instrumentation (WMI). Here are a few steps you can try to resolve the issue:
Reboot Your Computer: Sometimes, a simple reboot can resolve temporary issues. Restart your computer and try mounting the ISO again.
Check for System Corruption: Run the System File Checker (SFC) utility to scan and repair system files that may be corrupted.
sfc /scannow\n
Update Your System: Make sure your operating system is up-to-date. Check for Windows updates and install any pending updates.
Check WMI Service: Ensure that the Windows Management Instrumentation (WMI) service is running. You can do this through the Services application:
Press Win + R to open the Run dialog.
Type services.msc and press Enter.
Locate \"Windows Management Instrumentation\" in the list.
Make sure to set its status to \"Running\" and the startup type to \"Automatic.\"
Check for Security Software Interference: Security software can sometimes interfere with WMI operations. Temporarily disable your antivirus or security software and check if the issue persists.
Event Viewer: Check the Event Viewer for more detailed error information. Look for entries related to the 80041031 error and check if there are any additional details that can help identify the cause.
Press Win + X and select \"Event Viewer.\"
Navigate to \"Windows Logs\" -> \"Application\" or \"System.\"
Look for entries with the source related to WMI or the application use to mount the ISO.
ISO File Integrity: Ensure that the ISO file you are trying to mount is uncorrupted. Try mounting a different ISO file to see if the issue persists.
If the problem persists after trying these steps, additional troubleshooting is required. Consider seeking assistance from Microsoft support or community forums for more specific guidance based on your system configuration and the software you use to mount the ISO.
"},{"location":"contribute/","title":"How to Contribute?","text":""},{"location":"contribute/#testing","title":"Testing","text":"
Test the latest changes to WinUtil by running the pre-release and reporting issues you are encountering to help us continually improve WinUtil!
"},{"location":"contribute/#run-the-latest-pre-release","title":"Run the latest pre-release","text":"
irm christitus.com/windev | iex\n
Keep in mind
This is a pre-release and should be treated as such. It exists for developers to test the utility and report or fix bugs before they get added to the stable release. Don't use it in production!
If you encounter any challenges or problems with the script, I kindly request that you submit them via the \"Issues\" tab on the GitHub repository. By filling out the provided template, you can provide specific details about the issue, allowing me (and others in the community) to promptly address any bugs or consider feature requests.
Pull requests are now handled directly on the MAIN branch. This was done since we can now select specific releases to launch via releases in GitHub.
If you're doing code changes, then you can submit a PR to main branch, but I am very selective about these.
Important
Do not use a code formatter, make massive amounts of line changes, or make multiple feature changes. EACH FEATURE CHANGE SHOULD BE IT'S OWN PULL REQUEST!
When creating pull requests, it is essential to thoroughly document all changes made. This includes, but is not limited to, documenting any additions made to the tweaks section and corresponding undo tweak, so users are able to remove the newly added tweaks if necessary, and comprehensive documentation is required for all code changes. Document your changes and briefly explain why you made your changes in your Pull Request Description. Failure to adhere to this format may result in the denial of the pull request. Additionally, any code lacking sufficient documentation may also be denied.
By following these guidelines, we can maintain a high standard of quality and ensure that the codebase remains organized and well-documented.
Note
When creating a function, please include \"WPF\" or \"WinUtil\" in the file name so it can be loaded into the runspace.
%%{init: {\"flowchart\": {\"curve\": \"cardinal\"}} }%%\ngraph TD\n\u00a0 A[Fork Project] --> B[Clone Repository];\n\u00a0 B --> C[Create New Branch];\n\u00a0 C --> D[Make Changes];\n\u00a0 D --> G[Test Changes];\n\u00a0 G --> H{Tests Passed?};\n\u00a0 H -->|Yes| E[Commit Changes];\n\u00a0 H -->|No| J[Fix Issues];\n\u00a0 J --> G;\n\u00a0 E --> F[Push Branch];\n\u00a0 F --> K[Create Pull Request];\n\u00a0 K --> L[Fill out PR template];\n classDef default stroke:#333,stroke-width:4px,font-size:12pt;
Info
This is a diagram to guide you through the process. It may vary depending on the type of change you're making.
"},{"location":"contribute/#fork-the-repo","title":"Fork the Repo","text":"
Fork the WinUtil Repository here to create a copy that will be available in your repository list.
"},{"location":"contribute/#clone-the-fork","title":"Clone the Fork","text":"
Tip
While you can make your changes directly through the Web, we recommend cloning the repo to your device using the application GitHub Desktop (available in WinUtil) to test your fork easily.
Install GitHub Desktop if it is not already installed.
Log in using the same GitHub account you used to fork WinUtil.
Choose the fork under \"Your Repositories\" and press \"clone {repo name}\"
Create a new branch and name it something relatable to your changes.
Now you can modify WinUtil to your liking using your preferred text editor.
"},{"location":"contribute/#testing-your-changes","title":"Testing your changes","text":"
To test to see if your changes work as intended run following commands in a powershell teminal as admin:
Change the directory where you are running the commands to the forked project.
cd {path to the folder with the compile.ps1}
Run the following command to compile and run WinUtil:
.\\Compile.ps1 -run
After seeing that your changes work properly, feel free to commit the changes to the repository and make a PR. For help on that, follow the documentation below.
"},{"location":"contribute/#committing-the-changes","title":"Committing the changes","text":"
Before committing your changes, please discard changes made to the winutil.ps1 file, like the following:
Now, commit your changes once you are happy with the result.
Push the changes to upload them to your fork on github.com.
"},{"location":"contribute/#making-a-pr","title":"Making a PR","text":"
To make a PR on your repo under a new branch linking to the main branch, a button will show and say Preview and Create pull request. Click that button and fill in all the information that is provided on the template. Once all the information is filled in correctly, check your PR to make sure there is not a WinUtil.ps1 file attached to the PR. Once everything is good, make the PR and wait for Chris (the maintainer) to accept or deny your PR. Once it is accepted by Chris, you will be able to see your changes in the \"/windev\" build.
If you do not see your feature in the main \"/win\" build, that is fine. All new changes go into the /windev build to make sure everything is working OK before going fully public.
Congratulations! You just submitted your first PR. Thank you so much for contributing to WinUtil.
"},{"location":"devdocs/","title":"Table of Contents","text":""},{"location":"devdocs/#tweaks","title":"Tweaks","text":""},{"location":"devdocs/#z-advanced-tweaks-caution","title":"z--Advanced-Tweaks---CAUTION","text":"
Disable Search Box Web Suggestions in Registry(explorer restart)
Enable Daily Registry Backup Task 12.30am
Enable Legacy F8 Boot Recovery
Enable Search Box Web Suggestions in Registry(explorer restart)
HyperV Virtualization
Install Features
Legacy Media (WMP, DirectPlay)
NFS - Network File System
Windows Sandbox
Windows Subsystem for Linux
"},{"location":"faq/","title":"FAQ's","text":""},{"location":"faq/#how-do-i-uninstall-winutil","title":"How do I uninstall WinUtil?","text":"
You do not have to uninstall WinUtil. As it is a script you run from Powershell it only loads into your RAM. This means as soon as you close WinUtil it will be deleted off your system.
"},{"location":"faq/#i-applied-a-tweak-and-now-something-doesnt-work-what-do-i-do","title":"I applied a tweak and now something doesn't work, what do I do?","text":"
If you applied a tweak and it breaks something, you can always revert the tweak by selecting the tweak and clicking \"Undo Selected Tweaks\".
Essential Tweaks are modifications and optimizations that are generally safe for most users to implement. These tweaks are designed to enhance system performance, improve privacy, and reduce unnecessary system activities. They are considered low-risk and are recommended for users who want to ensure their system runs smoothly and efficiently without delving too deeply into complex configurations. The goal of Essential Tweaks is to provide noticeable improvements with minimal risk, making them suitable for a wide range of users, including those who may not have advanced technical knowledge.
Advanced Tweaks are intended for experienced users who have a solid understanding of their system and the potential implications of making deep-level changes. These tweaks involve more significant alterations to the operating system and can provide substantial customization. However, they also carry a higher risk of causing system instability or unintended side effects if not implemented correctly. Users who choose to apply Advanced Tweaks should proceed with caution, ensuring they have adequate knowledge and backups in place to recover if something goes wrong. These tweaks are not recommended for novice users or those unfamiliar with the inner workings of their operating system.
O&O ShutUp10++ can be launched from WinUtil with only one button click. It is a free privacy tool for Windows that lets users easily manage their privacy settings. It disables telemetry, controls updates, and manages app permissions to enhance security and privacy. The tool offers recommended settings for optimal privacy with just a few clicks.
The utility provides a convenient DNS selection feature, allowing users to choose between various DNS providers for both IPv4 and IPv6. This enables users to optimize their internet connection for speed, security, and privacy according to their specific needs. Here are the available options:
Default: Uses the default DNS settings configured by your ISP or network.
DHCP: Automatically acquires DNS settings from the DHCP server.
Google: A reliable and fast DNS service provided by Google.
Cloudflare: Known for speed and privacy, Cloudflare DNS is a popular choice for enhancing internet performance.
Cloudflare_Malware: Provides additional protection by blocking malware sites.
Cloudflare_Malware_Adult: Blocks both malware and adult content, offering more comprehensive filtering.
Level3: Another fast and reliable DNS service option.
Open_DNS: Offers customizable filtering and enhanced security features.
Quad9: Focuses on security by blocking known malicious domains.
The Customize Preferences section allows users to personalize their Windows experience by toggling various visual and functional features. These preferences are designed to enhance usability and tailor the system to the user\u2019s specific needs and preferences.
The Performance Plans section allows users to manage the Ultimate Performance Profile on their system. This feature is designed to optimize the system for maximum performance.
"},{"location":"userguide/#add-and-activate-the-ultimate-performance-profile","title":"Add and activate the Ultimate Performance Profile:","text":"
Enables and activates the Ultimate Performance Profile to enhance system performance by minimizing latency and increasing efficiency.
The utility provides three distinct settings for managing Windows updates: Default (Out of Box) Settings, Security (Recommended) Settings, and Disable ALL Updates (NOT RECOMMENDED!). Each setting offers a different approach to handling updates, catering to various user needs and preferences.
"},{"location":"userguide/#default-out-of-box-settings","title":"Default (Out of Box) Settings","text":"
Description: This setting retains the default configurations that come with Windows, ensuring no modifications are made.
Functionality: It will remove any custom Windows update settings previously applied.
Note: If update errors persist, reset all updates in the configuration tab to restore all Microsoft Update Services to their default settings, reinstalling them from their servers.
Description: This is the recommended setting for all computers.
Update Schedule:
Feature Updates: Delays feature updates by 2 years to avoid potential bugs and instability.
Security Updates: Installs security updates 4 days after their release to ensure system protection against pressing security flaws.
Rationale:
Feature Updates: Often introduce new features and bugs; delaying these updates minimizes the risk of system disruptions.
Security Updates: Essential for patching critical security vulnerabilities. Delaying them by a few days allows for verification of stability and compatibility without leaving the system exposed for extended periods.
"},{"location":"userguide/#disable-all-updates-not-recommended","title":"Disable ALL Updates (NOT RECOMMENDED!)","text":"
Description: This setting completely disables all Windows updates.
Suitability: May be appropriate for systems used for specific purposes that do not require active internet browsing.
Warning: Disabling updates significantly increases the risk of the system being hacked or infected due to the lack of security patches.
Note: It is strongly advised against using this setting due to the heightened security risks.
Bug
The Updates tab is currently non-functional. We are actively working on a resolution to restore its functionality.
If you don't have a Windows ISO file prepared, you can download it using the Media Creation Tool for the respective Windows version. Here is the Windows 11 version, and here is the Windows 10 version
Configure the debloat process.
Specify the target location for the new ISO file.
Let the magic happen!
Heads-up
This feature is still in development, and you may encounter some issues with the generated images. If that happens, don't hesitate to report an issue!
Download oscdimg.exe from the CTT GitHub repo will grab an OSCDIMG executable from the GitHub repository instead of a Chocolatey package.
Info
OSCDIMG is the tool that lets the program create ISO images. Typically, you would find this in the Windows Assessment and Deployment Kit
Selecting a scratch directory will copy the contents of the ISO file to the directory you specify instead of an automatically generated folder in the %TEMP% directory.
You can select an edition of Windows to debloat (SKU) using the convenient drop-down menu.
By default, MicroWin will debloat the Pro edition, but you can choose any edition you want.
Keep Provisioned Packages: leaving this option unticked (default) will try to remove every operating system package.
Some packages may remain after processing. This can happen if the packages in question are permanent or have been superseded by newer versions.
Keep Appx Packages: leaving this option unticked (default) will try to remove every Microsoft Store app from the Windows image.
This option will exclude some applications that are essential in the event that you want or need to add a Store app later on.
Keep Defender: leaving this option unticked will try to remove every part of Windows Defender, including the Windows Security app.
Leaving this option unticked is NOT recommended unless you plan to use a third-party antivirus solution on your MicroWin installation. In that regard, don't install AVs with bad reputations or rogueware.
Keep Edge: leaving this option unticked will try to remove every part of the Microsoft Edge browser using the best methods available.
Leaving this option unticked is not recommended because it might break some applications that might depend on the Edge WebView2 runtime. However, if that happens, you can easily reinstall it
Inject drivers will add the drivers in the folder that you specify to the target Windows image.
Import drivers from the current system will add every third-party driver that is present in your active installation.
This makes the target image have the same hardware compatibility as the active installation. However, this means that you will only be able to install the target Windows image and take full advantage of it on computers with the same hardware. To avoid this, you'll need to customize the install.wim file of the target ISO in the 'sources` folder.
Copy to Ventoy will copy the target ISO file to any USB drive with Ventoy installed
Info
Ventoy is a solution that lets you boot to any ISO file stored on a drive. Think of it as having multiple bootable USBs in one. Do note, though, that your drive needs to have enough free space for the target ISO file.
Some features are available through automation. This allows you to save your config file, pass it to WinUtil, walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
On the Install Tab, click \"Get Installed\", this will get all installed apps supported by Winutil on the system.
Click on the Settings cog in the upper right corner and choose Export. Choose file file and location; this will export the setting file.
Copy this file to a USB or somewhere you can use it after Windows installation.
Tip
Use the Microwin tab to create a custom Windows image & install the Windows image.
On any supported Windows machine, open PowerShell as Admin and run the following command to automatically apply tweaks and install apps from the config file.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/features/Features/DisableSearchSuggestions/","title":"Disable Search Box Web Suggestions in Registry(explorer restart)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/features/Features/EnableSearchSuggestions/","title":"Enable Search Box Web Suggestions in Registry(explorer restart)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows Sandbox is a lightweight virtual machine that provides a temporary desktop environment to safely run applications and programs in isolation.
Preview Code
{\n \"Content\": \"Windows Sandbox\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a021_\",\n \"Description\": \"Windows Sandbox is a lightweight virtual machine that provides a temporary desktop environment to safely run applications and programs in isolation.\",\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/Sandbox\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
.NET and .NET Framework is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
Preview Code
{\n \"Content\": \"All .Net Framework (2,3,4)\",\n \"Description\": \".NET and .NET Framework is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a010_\",\n \"feature\": [\n \"NetFx4-AdvSrvs\",\n \"NetFx3\"\n ],\n \"InvokeScript\": [],\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/dotnet\"\n}\n
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/dotnet/#features-to-install","title":"Features to install","text":"
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/hyperv/#features-to-install","title":"Features to install","text":"
"},{"location":"dev/features/Features/legacymedia/","title":"Legacy Media (WMP, DirectPlay)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/legacymedia/#features-to-install","title":"Features to install","text":"
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/nfs/#features-to-install","title":"Features to install","text":"
"},{"location":"dev/features/Features/wsl/","title":"Windows Subsystem for Linux","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows Subsystem for Linux is an optional feature of Windows that allows Linux programs to run natively on Windows without the need for a separate virtual machine or dual booting.
Preview Code
{\n \"Content\": \"Windows Subsystem for Linux\",\n \"Description\": \"Windows Subsystem for Linux is an optional feature of Windows that allows Linux programs to run natively on Windows without the need for a separate virtual machine or dual booting.\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a020_\",\n \"feature\": [\n \"VirtualMachinePlatform\",\n \"Microsoft-Windows-Subsystem-Linux\"\n ],\n \"InvokeScript\": [],\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/wsl\"\n}\n
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/wsl/#features-to-install","title":"Features to install","text":"
VirtualMachinePlatform
Microsoft-Windows-Subsystem-Linux
View the JSON file
"},{"location":"dev/features/Fixes/Autologin/","title":"Set Up Autologin","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFPanelDISM {\n <#\n\n .SYNOPSIS\n Checks for system corruption using Chkdsk, SFC, and DISM\n\n .DESCRIPTION\n 1. Chkdsk - Fixes disk and filesystem corruption\n 2. SFC Run 1 - Fixes system file corruption, and fixes DISM if it was corrupted\n 3. DISM - Fixes system image corruption, and fixes SFC's system image if it was corrupted\n 4. SFC Run 2 - Fixes system file corruption, this time with an almost guaranteed uncorrupted system image\n\n .NOTES\n Command Arguments:\n 1. Chkdsk\n /Scan - Runs an online scan on the system drive, attempts to fix any corruption, and queues other corruption for fixing on reboot\n 2. SFC\n /ScanNow - Performs a scan of the system files and fixes any corruption\n 3. DISM - Fixes system image corruption, and fixes SFC's system image if it was corrupted\n /Online - Fixes the currently running system image\n /Cleanup-Image - Performs cleanup operations on the image, could remove some unneeded temporary files\n /Restorehealth - Performs a scan of the image and fixes any corruption\n\n #>\n Start-Process PowerShell -ArgumentList \"Write-Host '(1/4) Chkdsk' -ForegroundColor Green; Chkdsk /scan;\n Write-Host '`n(2/4) SFC - 1st scan' -ForegroundColor Green; sfc /scannow;\n Write-Host '`n(3/4) DISM' -ForegroundColor Green; DISM /Online /Cleanup-Image /Restorehealth;\n Write-Host '`n(4/4) SFC - 2nd scan' -ForegroundColor Green; sfc /scannow;\n Read-Host '`nPress Enter to Continue'\" -verb runas\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFRunAdobeCCCleanerTool {\n <#\n .SYNOPSIS\n It removes or fixes problem files and resolves permission issues in registry keys.\n .DESCRIPTION\n The Creative Cloud Cleaner tool is a utility for experienced users to clean up corrupted installations.\n #>\n\n [string]$url=\"https://swupmf.adobe.com/webfeed/CleanerTool/win/AdobeCreativeCloudCleanerTool.exe\"\n\n Write-Host \"The Adobe Creative Cloud Cleaner tool is hosted at\"\n Write-Host \"$url\"\n\n try {\n # Don't show the progress because it will slow down the download speed\n $ProgressPreference='SilentlyContinue'\n\n Invoke-WebRequest -Uri $url -OutFile \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -UseBasicParsing -ErrorAction SilentlyContinue -Verbose\n\n # Revert back the ProgressPreference variable to the default value since we got the file desired\n $ProgressPreference='Continue'\n\n Start-Process -FilePath \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -Wait -ErrorAction SilentlyContinue -Verbose\n } catch {\n Write-Error $_.Exception.Message\n } finally {\n if (Test-Path -Path \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\") {\n Write-Host \"Cleaning up...\"\n Remove-Item -Path \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -Verbose\n }\n }\n}\n
View the JSON file
"},{"location":"dev/features/Fixes/Update/","title":"Reset Windows Update","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFFixesWinget {\n\n <#\n\n .SYNOPSIS\n Fixes Winget by running choco install winget\n .DESCRIPTION\n BravoNorris for the fantastic idea of a button to reinstall winget\n #>\n # Install Choco if not already present\n Install-WinUtilChoco\n Start-Process -FilePath \"choco\" -ArgumentList \"install winget -y --force\" -NoNewWindow -Wait\n\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/tweaks/Customize-Preferences/BingSearch/","title":"Bing Search in Start Menu","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If enable then includes web search results from Bing in your Start Menu search.
Preview Code
{\n \"Content\": \"Bing Search in Start Menu\",\n \"Description\": \"If enable then includes web search results from Bing in your Start Menu search.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a101_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/BingSearch\"\n}\n
function Invoke-WinUtilBingSearch {\n <#\n\n .SYNOPSIS\n Disables/Enables Bing Search\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Bing Search\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Bing Search\"\n $value = 1\n } else {\n Write-Host \"Disabling Bing Search\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Search\"\n Set-ItemProperty -Path $Path -Name BingSearchEnabled -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/DarkMode/","title":"Dark Theme for Windows","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then you will see a detailed Blue Screen of Death (BSOD) with more information.
Preview Code
{\n \"Content\": \"Detailed BSoD\",\n \"Description\": \"If Enabled then you will see a detailed Blue Screen of Death (BSOD) with more information.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a205_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/DetailedBSoD\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then Cursor movement is affected by the speed of your physical mouse movements.
Preview Code
{\n \"Content\": \"Mouse Acceleration\",\n \"Description\": \"If Enabled then Cursor movement is affected by the speed of your physical mouse movements.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a107_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/MouseAcceleration\"\n}\n
Function Invoke-WinUtilMouseAcceleration {\n <#\n\n .SYNOPSIS\n Enables/Disables Mouse Acceleration\n\n .PARAMETER DarkMoveEnabled\n Indicates the current Mouse Acceleration State\n\n #>\n Param($MouseAccelerationEnabled)\n try {\n if ($MouseAccelerationEnabled -eq $false) {\n Write-Host \"Enabling Mouse Acceleration\"\n $MouseSpeed = 1\n $MouseThreshold1 = 6\n $MouseThreshold2 = 10\n } else {\n Write-Host \"Disabling Mouse Acceleration\"\n $MouseSpeed = 0\n $MouseThreshold1 = 0\n $MouseThreshold2 = 0\n\n }\n\n $Path = \"HKCU:\\Control Panel\\Mouse\"\n Set-ItemProperty -Path $Path -Name MouseSpeed -Value $MouseSpeed\n Set-ItemProperty -Path $Path -Name MouseThreshold1 -Value $MouseThreshold1\n Set-ItemProperty -Path $Path -Name MouseThreshold2 -Value $MouseThreshold2\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/NumLock/","title":"NumLock on Startup","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Toggle the Num Lock key state when your computer starts.
Preview Code
{\n \"Content\": \"NumLock on Startup\",\n \"Description\": \"Toggle the Num Lock key state when your computer starts.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a102_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/NumLock\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If enabled then you will get suggestions to snap other applications in the left over spaces.
Preview Code
{\n \"Content\": \"Snap Assist Suggestion\",\n \"Description\": \"If enabled then you will get suggestions to snap other applications in the left over spaces.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a106_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/SnapSuggestion\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilSnapWindow {\n <#\n .SYNOPSIS\n Disables/Enables Snapping Windows on startup\n .PARAMETER Enabled\n Indicates whether to enable or disable Snapping Windows on startup\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Snap Windows On startup | Relogin Required\"\n $value = 1\n } else {\n Write-Host \"Disabling Snap Windows On startup | Relogin Required\"\n $value = 0\n }\n $Path = \"HKCU:\\Control Panel\\Desktop\"\n Set-ItemProperty -Path $Path -Name WindowArrangementActive -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then Sticky Keys is activated - Sticky keys is an accessibility feature of some graphical user interfaces which assists users who have physical disabilities or help users reduce repetitive strain injury.
Preview Code
{\n \"Content\": \"Sticky Keys\",\n \"Description\": \"If Enabled then Sticky Keys is activated - Sticky keys is an accessibility feature of some graphical user interfaces which assists users who have physical disabilities or help users reduce repetitive strain injury.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a108_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/StickyKeys\"\n}\n
Function Invoke-WinUtilStickyKeys {\n <#\n .SYNOPSIS\n Disables/Enables Sticky Keyss on startup\n .PARAMETER Enabled\n Indicates whether to enable or disable Sticky Keys on startup\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Sticky Keys On startup\"\n $value = 510\n } else {\n Write-Host \"Disabling Sticky Keys On startup\"\n $value = 58\n }\n $Path = \"HKCU:\\Control Panel\\Accessibility\\StickyKeys\"\n Set-ItemProperty -Path $Path -Name Flags -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskView/","title":"Task View Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
[Windows 11] If Enabled then the Taskbar Items will be shown on the Center, otherwise the Taskbar Items will be shown on the Left.
Preview Code
{\n \"Content\": \"Center Taskbar Items\",\n \"Description\": \"[Windows 11] If Enabled then the Taskbar Items will be shown on the Center, otherwise the Taskbar Items will be shown on the Left.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a204_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/TaskbarAlignment\"\n}\n
function Invoke-WinUtilTaskbarAlignment {\n <#\n\n .SYNOPSIS\n Switches between Center & Left Taskbar Alignment\n\n .PARAMETER Enabled\n Indicates whether to make Taskbar Alignment Center or Left\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Making Taskbar Alignment to the Center\"\n $value = 1\n } else {\n Write-Host \"Making Taskbar Alignment to the Left\"\n $value = 0\n }\n $Path = \"HKCU:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced\"\n Set-ItemProperty -Path $Path -Name \"TaskbarAl\" -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskbarSearch/","title":"Search Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilTaskbarSearch {\n <#\n\n .SYNOPSIS\n Enable/Disable Taskbar Search Button.\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Taskbar Search Button.\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Search Button\"\n $value = 1\n } else {\n Write-Host \"Disabling Search Button\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Search\\\"\n Set-ItemProperty -Path $Path -Name SearchboxTaskbarMode -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskbarWidgets/","title":"Widgets Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilTaskbarWidgets {\n <#\n\n .SYNOPSIS\n Enable/Disable Taskbar Widgets\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Taskbar Widgets\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Taskbar Widgets\"\n $value = 1\n } else {\n Write-Host \"Disabling Taskbar Widgets\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced\"\n Set-ItemProperty -Path $Path -Name TaskbarDa -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/VerboseLogon/","title":"Verbose Messages During Logon","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Show detailed messages during the login process for troubleshooting and diagnostics.
Preview Code
{\n \"Content\": \"Verbose Messages During Logon\",\n \"Description\": \"Show detailed messages during the login process for troubleshooting and diagnostics.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a103_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/VerboseLogon\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows 10 will not automatically install any games, third-party apps, or application links from the Windows Store for the signed-in user. Some default Apps will be inaccessible (eg. Phone Link)
Preview Code
{\n \"Content\": \"Disable ConsumerFeatures\",\n \"Description\": \"Windows 10 will not automatically install any games, third-party apps, or application links from the Windows Store for the signed-in user. Some default Apps will be inaccessible (eg. Phone Link)\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a003_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SOFTWARE\\\\Policies\\\\Microsoft\\\\Windows\\\\CloudContent\",\n \"OriginalValue\": \"0\",\n \"Name\": \"DisableWindowsConsumerFeatures\",\n \"Value\": \"1\",\n \"Type\": \"DWord\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/ConsumerFeatures\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/tweaks/Essential-Tweaks/DiskCleanup/","title":"Run Disk Cleanup","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/EndTaskOnTaskbar/","title":"Enable End Task With Right Click","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Hibernation is really meant for laptops as it saves what's in memory before turning the pc off. It really should never be used, but some people are lazy and rely on it. Don't be like Bob. Bob likes hibernation.
Preview Code
{\n \"Content\": \"Disable Hibernation\",\n \"Description\": \"Hibernation is really meant for laptops as it saves what's in memory before turning the pc off. It really should never be used, but some people are lazy and rely on it. Don't be like Bob. Bob likes hibernation.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a005_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\System\\\\CurrentControlSet\\\\Control\\\\Session Manager\\\\Power\",\n \"Name\": \"HibernateEnabled\",\n \"Type\": \"DWord\",\n \"Value\": \"0\",\n \"OriginalValue\": \"1\"\n },\n {\n \"Path\": \"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\FlyoutMenuSettings\",\n \"Name\": \"ShowHibernateOption\",\n \"Type\": \"DWord\",\n \"Value\": \"0\",\n \"OriginalValue\": \"1\"\n }\n ],\n \"InvokeScript\": [\n \"powercfg.exe /hibernate off\"\n ],\n \"UndoScript\": [\n \"powercfg.exe /hibernate on\"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Hiber\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Disables HomeGroup - HomeGroup is a password-protected home networking service that lets you share your stuff with other PCs that are currently running and connected to your network.
Preview Code
{\n \"Content\": \"Disable Homegroup\",\n \"Description\": \"Disables HomeGroup - HomeGroup is a password-protected home networking service that lets you share your stuff with other PCs that are currently running and connected to your network.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a005_\",\n \"service\": [\n {\n \"Name\": \"HomeGroupListener\",\n \"StartupType\": \"Manual\",\n \"OriginalType\": \"Automatic\"\n },\n {\n \"Name\": \"HomeGroupProvider\",\n \"StartupType\": \"Manual\",\n \"OriginalType\": \"Automatic\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Home\"\n}\n
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/LaptopHibernation/","title":"Set Hibernation as default (good for laptops)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Most modern laptops have connected standby enabled which drains the battery, this sets hibernation as default which will not drain the battery. See issue https://github.com/ChrisTitusTech/winutil/issues/1399
Preview Code
{\n \"Content\": \"Set Hibernation as default (good for laptops)\",\n \"Description\": \"Most modern laptops have connected standby enabled which drains the battery, this sets hibernation as default which will not drain the battery. See issue https://github.com/ChrisTitusTech/winutil/issues/1399\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a014_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\Power\\\\PowerSettings\\\\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\\\\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0\",\n \"OriginalValue\": \"1\",\n \"Name\": \"Attributes\",\n \"Value\": \"2\",\n \"Type\": \"DWord\"\n },\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\Power\\\\PowerSettings\\\\abfc2519-3608-4c2a-94ea-171b0ed546ab\\\\94ac6d29-73ce-41a6-809f-6363ba21b47e\",\n \"OriginalValue\": \"0\",\n \"Name\": \"Attributes \",\n \"Value\": \"2\",\n \"Type\": \"DWord\"\n }\n ],\n \"InvokeScript\": [\n \"\n Write-Host \\\"Turn on Hibernation\\\"\n Start-Process -FilePath powercfg -ArgumentList \\\"/hibernate on\\\" -NoNewWindow -Wait\n\n # Set hibernation as the default action\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-ac 60\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-dc 60\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-ac 10\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-dc 1\\\" -NoNewWindow -Wait\n \"\n ],\n \"UndoScript\": [\n \"\n Write-Host \\\"Turn off Hibernation\\\"\n Start-Process -FilePath powercfg -ArgumentList \\\"/hibernate off\\\" -NoNewWindow -Wait\n\n # Set standby to detault values\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-ac 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-dc 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-ac 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-dc 15\\\" -NoNewWindow -Wait\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/LaptopHibernation\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/Powershell7/","title":"Change Windows Terminal default: PowerShell 5 -> PowerShell 7","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFTweakPS7{\n <#\n .SYNOPSIS\n This will edit the config file of the Windows Terminal Replacing the Powershell 5 to Powershell 7 and install Powershell 7 if necessary\n .PARAMETER action\n PS7: Configures Powershell 7 to be the default Terminal\n PS5: Configures Powershell 5 to be the default Terminal\n #>\n param (\n [ValidateSet(\"PS7\", \"PS5\")]\n [string]$action\n )\n\n switch ($action) {\n \"PS7\"{\n if (Test-Path -Path \"$env:ProgramFiles\\PowerShell\\7\") {\n Write-Host \"Powershell 7 is already installed.\"\n } else {\n Write-Host \"Installing Powershell 7...\"\n Invoke-WinUtilWingetProgram -Action Install -Programs @(\"Microsoft.PowerShell\")\n }\n $targetTerminalName = \"PowerShell\"\n }\n \"PS5\"{\n $targetTerminalName = \"Windows PowerShell\"\n }\n }\n # Check if the Windows Terminal is installed and return if not (Prerequisite for the following code)\n if (-not (Get-Command \"wt\" -ErrorAction SilentlyContinue)) {\n Write-Host \"Windows Terminal not installed. Skipping Terminal preference\"\n return\n }\n # Check if the Windows Terminal settings.json file exists and return if not (Prereqisite for the following code)\n $settingsPath = \"$env:LOCALAPPDATA\\Packages\\Microsoft.WindowsTerminal_8wekyb3d8bbwe\\LocalState\\settings.json\"\n if (-not (Test-Path -Path $settingsPath)) {\n Write-Host \"Windows Terminal Settings file not found at $settingsPath\"\n return\n }\n\n Write-Host \"Settings file found.\"\n $settingsContent = Get-Content -Path $settingsPath | ConvertFrom-Json\n $ps7Profile = $settingsContent.profiles.list | Where-Object { $_.name -eq $targetTerminalName }\n if ($ps7Profile) {\n $settingsContent.defaultProfile = $ps7Profile.guid\n $updatedSettings = $settingsContent | ConvertTo-Json -Depth 100\n Set-Content -Path $settingsPath -Value $updatedSettings\n Write-Host \"Default profile updated to \" -NoNewline\n Write-Host \"$targetTerminalName \" -ForegroundColor White -NoNewline\n Write-Host \"using the name attribute.\"\n } else {\n Write-Host \"No PowerShell 7 profile found in Windows Terminal settings using the name attribute.\"\n }\n}\n
Function Invoke-WinUtilWingetProgram {\n <#\n .SYNOPSIS\n Runs the designated action on the provided programs using Winget\n\n .PARAMETER Programs\n A list of programs to process\n\n .PARAMETER action\n The action to perform on the programs, can be either 'Install' or 'Uninstall'\n\n .NOTES\n The triple quotes are required any time you need a \" in a normal script block.\n The winget Return codes are documented here: https://github.com/microsoft/winget-cli/blob/master/doc/windows/package-actionr/winget/returnCodes.md\n #>\n\n param(\n [Parameter(Mandatory, Position=0)]$Programs,\n\n [Parameter(Mandatory, Position=1)]\n [ValidateSet(\"Install\", \"Uninstall\")]\n [String]$Action\n )\n\n Function Invoke-Winget {\n <#\n .SYNOPSIS\n Invokes the winget.exe with the provided arguments and return the exit code\n\n .PARAMETER wingetId\n The Id of the Program that Winget should Install/Uninstall\n\n .PARAMETER scope\n Determines the installation mode. Can be \"user\" or \"machine\" (For more info look at the winget documentation)\n\n .PARAMETER credential\n The PSCredential Object of the user that should be used to run winget\n\n .NOTES\n Invoke Winget uses the public variable $Action defined outside the function to determine if a Program should be installed or removed\n #>\n param (\n [string]$wingetId,\n [string]$scope = \"\",\n [PScredential]$credential = $null\n )\n\n $commonArguments = \"--id $wingetId --silent\"\n $arguments = if ($Action -eq \"Install\") {\n \"install $commonArguments --accept-source-agreements --accept-package-agreements $(if ($scope) {\" --scope $scope\"})\"\n } else {\n \"uninstall $commonArguments\"\n }\n\n $processParams = @{\n FilePath = \"winget\"\n ArgumentList = $arguments\n Wait = $true\n PassThru = $true\n NoNewWindow = $true\n }\n\n if ($credential) {\n $processParams.credential = $credential\n }\n\n return (Start-Process @processParams).ExitCode\n }\n\n Function Invoke-Install {\n <#\n .SYNOPSIS\n Contains the Install Logic and return code handling from winget\n\n .PARAMETER Program\n The Winget ID of the Program that should be installed\n #>\n param (\n [string]$Program\n )\n $status = Invoke-Winget -wingetId $Program\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully.\"\n return $true\n } elseif ($status -eq -1978335189) {\n Write-Host \"$($Program) No applicable update found\"\n return $true\n }\n\n Write-Host \"Attempt installation of $($Program) with User scope\"\n $status = Invoke-Winget -wingetId $Program -scope \"user\"\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully with User scope.\"\n return $true\n } elseif ($status -eq -1978335189) {\n Write-Host \"$($Program) No applicable update found\"\n return $true\n }\n\n $userChoice = [System.Windows.MessageBox]::Show(\"Do you want to attempt $($Program) installation with specific user credentials? Select 'Yes' to proceed or 'No' to skip.\", \"User credential Prompt\", [System.Windows.MessageBoxButton]::YesNo)\n if ($userChoice -eq 'Yes') {\n $getcreds = Get-Credential\n $status = Invoke-Winget -wingetId $Program -credential $getcreds\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully with User prompt.\"\n return $true\n }\n } else {\n Write-Host \"Skipping installation with specific user credentials.\"\n }\n\n Write-Host \"Failed to install $($Program).\"\n return $false\n }\n\n Function Invoke-Uninstall {\n <#\n .SYNOPSIS\n Contains the Uninstall Logic and return code handling from winget\n\n .PARAMETER Program\n The Winget ID of the Program that should be uninstalled\n #>\n param (\n [psobject]$Program\n )\n\n try {\n $status = Invoke-Winget -wingetId $Program\n if ($status -eq 0) {\n Write-Host \"$($Program) uninstalled successfully.\"\n return $true\n } else {\n Write-Host \"Failed to uninstall $($Program).\"\n return $false\n }\n } catch {\n Write-Host \"Failed to uninstall $($Program) due to an error: $_\"\n return $false\n }\n }\n\n $count = $Programs.Count\n $failedPackages = @()\n\n Write-Host \"===========================================\"\n Write-Host \"-- Configuring winget packages ---\"\n Write-Host \"===========================================\"\n\n for ($i = 0; $i -lt $count; $i++) {\n $Program = $Programs[$i]\n $result = $false\n Set-WinUtilProgressBar -label \"$Action $($Program)\" -percent ($i / $count * 100)\n $sync.form.Dispatcher.Invoke([action]{ Set-WinUtilTaskbaritem -value ($i / $count)})\n\n $result = switch ($Action) {\n \"Install\" {Invoke-Install -Program $Program}\n \"Uninstall\" {Invoke-Uninstall -Program $Program}\n default {throw \"[Install-WinUtilProgramWinget] Invalid action: $Action\"}\n }\n\n if (-not $result) {\n $failedPackages += $Program\n }\n }\n\n Set-WinUtilProgressBar -label \"$($Action)ation done\" -percent 100\n return $failedPackages\n}\n
function Set-WinUtilProgressbar{\n <#\n .SYNOPSIS\n This function is used to Update the Progress Bar displayed in the winutil GUI.\n It will be automatically hidden if the user clicks something and no process is running\n .PARAMETER Label\n The Text to be overlayed onto the Progress Bar\n .PARAMETER PERCENT\n The percentage of the Progress Bar that should be filled (0-100)\n .PARAMETER Hide\n If provided, the Progress Bar and the label will be hidden\n #>\n param(\n [string]$Label,\n [ValidateRange(0,100)]\n [int]$Percent,\n $Hide\n )\n if ($hide) {\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Visibility = \"Collapsed\"})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBar.Visibility = \"Collapsed\"})\n } else {\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Visibility = \"Visible\"})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBar.Visibility = \"Visible\"})\n }\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Content.Text = $label})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Content.ToolTip = $label})\n $sync.form.Dispatcher.Invoke([action]{ $sync.ProgressBar.Value = $percent})\n\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
This will create an Environment Variable called 'POWERSHELL_TELEMETRY_OPTOUT' with a value of '1' which will tell Powershell 7 to not send Telemetry Data.
Preview Code
{\n \"Content\": \"Disable Powershell 7 Telemetry\",\n \"Description\": \"This will create an Environment Variable called 'POWERSHELL_TELEMETRY_OPTOUT' with a value of '1' which will tell Powershell 7 to not send Telemetry Data.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a009_\",\n \"InvokeScript\": [\n \"[Environment]::SetEnvironmentVariable('POWERSHELL_TELEMETRY_OPTOUT', '1', 'Machine')\"\n ],\n \"UndoScript\": [\n \"[Environment]::SetEnvironmentVariable('POWERSHELL_TELEMETRY_OPTOUT', '', 'Machine')\"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Powershell7Tele\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Creates a restore point at runtime in case a revert is needed from WinUtil modifications
Preview Code
{\n \"Content\": \"Create Restore Point\",\n \"Description\": \"Creates a restore point at runtime in case a revert is needed from WinUtil modifications\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Checked\": \"False\",\n \"Order\": \"a001_\",\n \"InvokeScript\": [\n \"\n # Check if the user has administrative privileges\n if (-Not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {\n Write-Host \\\"Please run this script as an administrator.\\\"\n return\n }\n\n # Check if System Restore is enabled for the main drive\n try {\n # Try getting restore points to check if System Restore is enabled\n Enable-ComputerRestore -Drive \\\"$env:SystemDrive\\\"\n } catch {\n Write-Host \\\"An error occurred while enabling System Restore: $_\\\"\n }\n\n # Check if the SystemRestorePointCreationFrequency value exists\n $exists = Get-ItemProperty -path \\\"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows NT\\\\CurrentVersion\\\\SystemRestore\\\" -Name \\\"SystemRestorePointCreationFrequency\\\" -ErrorAction SilentlyContinue\n if($null -eq $exists) {\n write-host 'Changing system to allow multiple restore points per day'\n Set-ItemProperty -Path \\\"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows NT\\\\CurrentVersion\\\\SystemRestore\\\" -Name \\\"SystemRestorePointCreationFrequency\\\" -Value \\\"0\\\" -Type DWord -Force -ErrorAction Stop | Out-Null\n }\n\n # Attempt to load the required module for Get-ComputerRestorePoint\n try {\n Import-Module Microsoft.PowerShell.Management -ErrorAction Stop\n } catch {\n Write-Host \\\"Failed to load the Microsoft.PowerShell.Management module: $_\\\"\n return\n }\n\n # Get all the restore points for the current day\n try {\n $existingRestorePoints = Get-ComputerRestorePoint | Where-Object { $_.CreationTime.Date -eq (Get-Date).Date }\n } catch {\n Write-Host \\\"Failed to retrieve restore points: $_\\\"\n return\n }\n\n # Check if there is already a restore point created today\n if ($existingRestorePoints.Count -eq 0) {\n $description = \\\"System Restore Point created by WinUtil\\\"\n\n Checkpoint-Computer -Description $description -RestorePointType \\\"MODIFY_SETTINGS\\\"\n Write-Host -ForegroundColor Green \\\"System Restore Point Created Successfully\\\"\n }\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/RestorePoint\"\n}\n
# Check if the user has administrative privileges\n if (-Not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {\n Write-Host \"Please run this script as an administrator.\"\n return\n }\n\n # Check if System Restore is enabled for the main drive\n try {\n # Try getting restore points to check if System Restore is enabled\n Enable-ComputerRestore -Drive \"$env:SystemDrive\"\n } catch {\n Write-Host \"An error occurred while enabling System Restore: $_\"\n }\n\n # Check if the SystemRestorePointCreationFrequency value exists\n $exists = Get-ItemProperty -path \"HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SystemRestore\" -Name \"SystemRestorePointCreationFrequency\" -ErrorAction SilentlyContinue\n if($null -eq $exists) {\n write-host 'Changing system to allow multiple restore points per day'\n Set-ItemProperty -Path \"HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SystemRestore\" -Name \"SystemRestorePointCreationFrequency\" -Value \"0\" -Type DWord -Force -ErrorAction Stop | Out-Null\n }\n\n # Attempt to load the required module for Get-ComputerRestorePoint\n try {\n Import-Module Microsoft.PowerShell.Management -ErrorAction Stop\n } catch {\n Write-Host \"Failed to load the Microsoft.PowerShell.Management module: $_\"\n return\n }\n\n # Get all the restore points for the current day\n try {\n $existingRestorePoints = Get-ComputerRestorePoint | Where-Object { $_.CreationTime.Date -eq (Get-Date).Date }\n } catch {\n Write-Host \"Failed to retrieve restore points: $_\"\n return\n }\n\n # Check if there is already a restore point created today\n if ($existingRestorePoints.Count -eq 0) {\n $description = \"System Restore Point created by WinUtil\"\n\n Checkpoint-Computer -Description $description -RestorePointType \"MODIFY_SETTINGS\"\n Write-Host -ForegroundColor Green \"System Restore Point Created Successfully\"\n }\n
View the JSON file
"},{"location":"dev/tweaks/Essential-Tweaks/Services/","title":"Set Services to Manual","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Turns a bunch of system services to manual that don't need to be running all the time. This is pretty harmless as if the service is needed, it will simply start on demand.
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
Windows scheduled tasks are used to run scripts or programs at specific times or events. Disabling unnecessary tasks can improve system performance and reduce unwanted background activity.
You can find information about scheduled tasks on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Performance-Plans/AddUltPerf/","title":"Add and Activate Ultimate Performance Profile","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Invoke-WPFUltimatePerformance {\n <#\n\n .SYNOPSIS\n Creates or removes the Ultimate Performance power scheme\n\n .PARAMETER State\n Indicates whether to enable or disable the Ultimate Performance power scheme\n\n #>\n param($State)\n try {\n # Check if Ultimate Performance plan is installed\n $ultimatePlan = powercfg -list | Select-String -Pattern \"Ultimate Performance\"\n if($state -eq \"Enable\") {\n if ($ultimatePlan) {\n Write-Host \"Ultimate Performance plan is already installed.\"\n } else {\n Write-Host \"Installing Ultimate Performance plan...\"\n powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61\n Write-Host \"> Ultimate Performance plan installed.\"\n }\n\n # Set the Ultimate Performance plan as active\n $ultimatePlanGUID = (powercfg -list | Select-String -Pattern \"Ultimate Performance\").Line.Split()[3]\n powercfg -setactive $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan is now active.\"\n\n\n }\n elseif($state -eq \"Disable\") {\n if ($ultimatePlan) {\n # Extract the GUID of the Ultimate Performance plan\n $ultimatePlanGUID = $ultimatePlan.Line.Split()[3]\n\n # Set a different power plan as active before deleting the Ultimate Performance plan\n $balancedPlanGUID = (powercfg -list | Select-String -Pattern \"Balanced\").Line.Split()[3]\n powercfg -setactive $balancedPlanGUID\n\n # Delete the Ultimate Performance plan\n powercfg -delete $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan has been uninstalled.\"\n Write-Host \"> Balanced plan is now active.\"\n } else {\n Write-Host \"Ultimate Performance plan is not installed.\"\n }\n }\n } catch {\n Write-Warning $psitem.Exception.Message\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Invoke-WPFUltimatePerformance {\n <#\n\n .SYNOPSIS\n Creates or removes the Ultimate Performance power scheme\n\n .PARAMETER State\n Indicates whether to enable or disable the Ultimate Performance power scheme\n\n #>\n param($State)\n try {\n # Check if Ultimate Performance plan is installed\n $ultimatePlan = powercfg -list | Select-String -Pattern \"Ultimate Performance\"\n if($state -eq \"Enable\") {\n if ($ultimatePlan) {\n Write-Host \"Ultimate Performance plan is already installed.\"\n } else {\n Write-Host \"Installing Ultimate Performance plan...\"\n powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61\n Write-Host \"> Ultimate Performance plan installed.\"\n }\n\n # Set the Ultimate Performance plan as active\n $ultimatePlanGUID = (powercfg -list | Select-String -Pattern \"Ultimate Performance\").Line.Split()[3]\n powercfg -setactive $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan is now active.\"\n\n\n }\n elseif($state -eq \"Disable\") {\n if ($ultimatePlan) {\n # Extract the GUID of the Ultimate Performance plan\n $ultimatePlanGUID = $ultimatePlan.Line.Split()[3]\n\n # Set a different power plan as active before deleting the Ultimate Performance plan\n $balancedPlanGUID = (powercfg -list | Select-String -Pattern \"Balanced\").Line.Split()[3]\n powercfg -setactive $balancedPlanGUID\n\n # Delete the Ultimate Performance plan\n powercfg -delete $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan has been uninstalled.\"\n Write-Host \"> Balanced plan is now active.\"\n } else {\n Write-Host \"Ultimate Performance plan is not installed.\"\n }\n }\n } catch {\n Write-Warning $psitem.Exception.Message\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFShortcut {\n <#\n\n .SYNOPSIS\n Creates a shortcut and prompts for a save location\n\n .PARAMETER ShortcutToAdd\n The name of the shortcut to add\n\n .PARAMETER RunAsAdmin\n A boolean value to make 'Run as administrator' property on (true) or off (false), defaults to off\n\n #>\n param(\n $ShortcutToAdd,\n [bool]$RunAsAdmin = $false\n )\n\n # Preper the Shortcut Fields and add an a Custom Icon if it's available, else don't add a Custom Icon.\n\n Switch ($ShortcutToAdd) {\n \"WinUtil\" {\n # Use Powershell 7 if installed and fallback to PS5 if not\n if (Get-Command \"pwsh\" -ErrorAction SilentlyContinue) {\n $shell = \"pwsh.exe\"\n } else {\n $shell = \"powershell.exe\"\n }\n\n $shellArgs = \"-ExecutionPolicy Bypass -Command `\"Start-Process $shell -verb runas -ArgumentList `'-Command `\"irm https://github.com/ChrisTitusTech/winutil/releases/latest/download/winutil.ps1 | iex`\"`'\"\n\n $DestinationName = \"WinUtil.lnk\"\n }\n }\n\n # Show a File Dialog Browser, to let the User choose the Name and Location of where to save the Shortcut\n $FileBrowser = New-Object System.Windows.Forms.SaveFileDialog\n $FileBrowser.InitialDirectory = [Environment]::GetFolderPath('Desktop')\n $FileBrowser.Filter = \"Shortcut Files (*.lnk)|*.lnk\"\n $FileBrowser.FileName = $DestinationName\n\n # Do an Early Return if the Save Operation was canceled by User's Input.\n $FileBrowserResult = $FileBrowser.ShowDialog()\n $DialogResultEnum = New-Object System.Windows.Forms.DialogResult\n if (-not ($FileBrowserResult -eq $DialogResultEnum::OK)) {\n return\n }\n\n # Prepare the Shortcut paramter\n $WshShell = New-Object -comObject WScript.Shell\n $Shortcut = $WshShell.CreateShortcut($FileBrowser.FileName)\n $Shortcut.TargetPath = $shell\n $Shortcut.Arguments = $shellArgs\n if (Test-Path -Path $winutildir[\"logo.ico\"]) {\n $shortcut.IconLocation = $winutildir[\"logo.ico\"]\n }\n\n # Save the Shortcut to disk\n $Shortcut.Save()\n\n if ($RunAsAdmin -eq $true) {\n $bytes = [System.IO.File]::ReadAllBytes($FileBrowser.FileName)\n # Set byte value at position 0x15 in hex, or 21 in decimal, from the value 0x00 to 0x20 in hex\n $bytes[0x15] = $bytes[0x15] -bor 0x20\n [System.IO.File]::WriteAllBytes($FileBrowser.FileName, $bytes)\n }\n\n Write-Host \"Shortcut for $ShortcutToAdd has been saved to $($FileBrowser.FileName) with 'Run as administrator' set to $RunAsAdmin\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
# Define the local path of the HOSTS file\n $localHostsPath = \"C:\\Windows\\System32\\drivers\\etc\\hosts\"\n\n # Load the content of the HOSTS file\n try {\n $hostsContent = Get-Content $localHostsPath -ErrorAction Stop\n } catch {\n Write-Error \"Failed to load the HOSTS file. Error: $_\"\n return\n }\n\n # Initialize flags and buffer for new content\n $recording = $true\n $newContent = @()\n\n # Iterate over each line of the HOSTS file\n foreach ($line in $hostsContent) {\n if ($line -match \"#AdobeNetBlock-start\") {\n $recording = $false\n }\n if ($recording) {\n $newContent += $line\n }\n if ($line -match \"#AdobeNetBlock-end\") {\n $recording = $true\n }\n }\n\n # Write the filtered content back to the HOSTS file\n try {\n $newContent | Set-Content $localHostsPath -Encoding ASCII\n Write-Output \"Successfully removed the AdobeNetBlock section from the HOSTS file.\"\n } catch {\n Write-Error \"Failed to write back to the HOSTS file. Error: $_\"\n }\n\n # Flush the DNS resolver cache\n try {\n Invoke-Expression \"ipconfig /flushdns\"\n Write-Output \"DNS cache flushed successfully.\"\n } catch {\n Write-Error \"Failed to flush DNS cache. Error: $_\"\n }\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/DeBloat/","title":"Remove ALL MS Store Apps - NOT RECOMMENDED","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
USE WITH CAUTION!!!!! This will remove ALL Microsoft store apps other than the essentials to make winget work. Games installed by MS Store ARE INCLUDED!
Preview Code
{\n \"Content\": \"Remove ALL MS Store Apps - NOT RECOMMENDED\",\n \"Description\": \"USE WITH CAUTION!!!!! This will remove ALL Microsoft store apps other than the essentials to make winget work. Games installed by MS Store ARE INCLUDED!\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a028_\",\n \"appx\": [\n \"Microsoft.Microsoft3DViewer\",\n \"Microsoft.AppConnector\",\n \"Microsoft.BingFinance\",\n \"Microsoft.BingNews\",\n \"Microsoft.BingSports\",\n \"Microsoft.BingTranslator\",\n \"Microsoft.BingWeather\",\n \"Microsoft.BingFoodAndDrink\",\n \"Microsoft.BingHealthAndFitness\",\n \"Microsoft.BingTravel\",\n \"Microsoft.MinecraftUWP\",\n \"Microsoft.GamingServices\",\n \"Microsoft.GetHelp\",\n \"Microsoft.Getstarted\",\n \"Microsoft.Messaging\",\n \"Microsoft.Microsoft3DViewer\",\n \"Microsoft.MicrosoftSolitaireCollection\",\n \"Microsoft.NetworkSpeedTest\",\n \"Microsoft.News\",\n \"Microsoft.Office.Lens\",\n \"Microsoft.Office.Sway\",\n \"Microsoft.Office.OneNote\",\n \"Microsoft.OneConnect\",\n \"Microsoft.People\",\n \"Microsoft.Print3D\",\n \"Microsoft.SkypeApp\",\n \"Microsoft.Wallet\",\n \"Microsoft.Whiteboard\",\n \"Microsoft.WindowsAlarms\",\n \"microsoft.windowscommunicationsapps\",\n \"Microsoft.WindowsFeedbackHub\",\n \"Microsoft.WindowsMaps\",\n \"Microsoft.YourPhone\",\n \"Microsoft.WindowsSoundRecorder\",\n \"Microsoft.XboxApp\",\n \"Microsoft.ConnectivityStore\",\n \"Microsoft.ScreenSketch\",\n \"Microsoft.Xbox.TCUI\",\n \"Microsoft.XboxGameOverlay\",\n \"Microsoft.XboxGameCallableUI\",\n \"Microsoft.XboxSpeechToTextOverlay\",\n \"Microsoft.MixedReality.Portal\",\n \"Microsoft.XboxIdentityProvider\",\n \"Microsoft.ZuneMusic\",\n \"Microsoft.ZuneVideo\",\n \"Microsoft.Getstarted\",\n \"Microsoft.MicrosoftOfficeHub\",\n \"*EclipseManager*\",\n \"*ActiproSoftwareLLC*\",\n \"*AdobeSystemsIncorporated.AdobePhotoshopExpress*\",\n \"*Duolingo-LearnLanguagesforFree*\",\n \"*PandoraMediaInc*\",\n \"*CandyCrush*\",\n \"*BubbleWitch3Saga*\",\n \"*Wunderlist*\",\n \"*Flipboard*\",\n \"*Twitter*\",\n \"*Facebook*\",\n \"*Royal Revolt*\",\n \"*Sway*\",\n \"*Speed Test*\",\n \"*Dolby*\",\n \"*Viber*\",\n \"*ACGMediaPlayer*\",\n \"*Netflix*\",\n \"*OneCalendar*\",\n \"*LinkedInforWindows*\",\n \"*HiddenCityMysteryofShadows*\",\n \"*Hulu*\",\n \"*HiddenCity*\",\n \"*AdobePhotoshopExpress*\",\n \"*HotspotShieldFreeVPN*\",\n \"*Microsoft.Advertising.Xaml*\"\n ],\n \"InvokeScript\": [\n \"\n $TeamsPath = [System.IO.Path]::Combine($env:LOCALAPPDATA, 'Microsoft', 'Teams')\n $TeamsUpdateExePath = [System.IO.Path]::Combine($TeamsPath, 'Update.exe')\n\n Write-Host \\\"Stopping Teams process...\\\"\n Stop-Process -Name \\\"*teams*\\\" -Force -ErrorAction SilentlyContinue\n\n Write-Host \\\"Uninstalling Teams from AppData\\\\Microsoft\\\\Teams\\\"\n if ([System.IO.File]::Exists($TeamsUpdateExePath)) {\n # Uninstall app\n $proc = Start-Process $TeamsUpdateExePath \\\"-uninstall -s\\\" -PassThru\n $proc.WaitForExit()\n }\n\n Write-Host \\\"Removing Teams AppxPackage...\\\"\n Get-AppxPackage \\\"*Teams*\\\" | Remove-AppxPackage -ErrorAction SilentlyContinue\n Get-AppxPackage \\\"*Teams*\\\" -AllUsers | Remove-AppxPackage -AllUsers -ErrorAction SilentlyContinue\n\n Write-Host \\\"Deleting Teams directory\\\"\n if ([System.IO.Directory]::Exists($TeamsPath)) {\n Remove-Item $TeamsPath -Force -Recurse -ErrorAction SilentlyContinue\n }\n\n Write-Host \\\"Deleting Teams uninstall registry key\\\"\n # Uninstall from Uninstall registry key UninstallString\n $us = (Get-ChildItem -Path HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Uninstall, HKLM:\\\\SOFTWARE\\\\Wow6432Node\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Uninstall | Get-ItemProperty | Where-Object { $_.DisplayName -like '*Teams*'}).UninstallString\n if ($us.Length -gt 0) {\n $us = ($us.Replace('/I', '/uninstall ') + ' /quiet').Replace(' ', ' ')\n $FilePath = ($us.Substring(0, $us.IndexOf('.exe') + 4).Trim())\n $ProcessArgs = ($us.Substring($us.IndexOf('.exe') + 5).Trim().replace(' ', ' '))\n $proc = Start-Process -FilePath $FilePath -Args $ProcessArgs -PassThru\n $proc.WaitForExit()\n }\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DeBloat\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function CCStopper {\n $path = \"C:\\Program Files (x86)\\Common Files\\Adobe\\Adobe Desktop Common\\ADS\\Adobe Desktop Service.exe\"\n\n # Test if the path exists before proceeding\n if (Test-Path $path) {\n Takeown /f $path\n $acl = Get-Acl $path\n $acl.SetOwner([System.Security.Principal.NTAccount]\"Administrators\")\n $acl | Set-Acl $path\n\n Rename-Item -Path $path -NewName \"Adobe Desktop Service.exe.old\" -Force\n } else {\n Write-Host \"Adobe Desktop Service is not in the default location.\"\n }\n }\n\n\n function AcrobatUpdates {\n # Editing Acrobat Updates. The last folder before the key is dynamic, therefore using a script.\n # Possible Values for the edited key:\n # 0 = Do not download or install updates automatically\n # 2 = Automatically download updates but let the user choose when to install them\n # 3 = Automatically download and install updates (default value)\n # 4 = Notify the user when an update is available but don't download or install it automatically\n # = It notifies the user using Windows Notifications. It runs on startup without having to have a Service/Acrobat/Reader running, therefore 0 is the next best thing.\n\n $rootPath = \"HKLM:\\SOFTWARE\\WOW6432Node\\Adobe\\Adobe ARM\\Legacy\\Acrobat\"\n\n # Get all subkeys under the specified root path\n $subKeys = Get-ChildItem -Path $rootPath | Where-Object { $_.PSChildName -like \"{*}\" }\n\n # Loop through each subkey\n foreach ($subKey in $subKeys) {\n # Get the full registry path\n $fullPath = Join-Path -Path $rootPath -ChildPath $subKey.PSChildName\n try {\n Set-ItemProperty -Path $fullPath -Name Mode -Value 0\n Write-Host \"Acrobat Updates have been disabled.\"\n } catch {\n Write-Host \"Registry Key for changing Acrobat Updates does not exist in $fullPath\"\n }\n }\n }\n\n CCStopper\n AcrobatUpdates\n
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Disables all Microsoft Store apps from running in the background, which has to be done individually since Win11
Preview Code
{\n \"Content\": \"Disable Background Apps\",\n \"Description\": \"Disables all Microsoft Store apps from running in the background, which has to be done individually since Win11\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a024_\",\n \"registry\": [\n {\n \"Path\": \"HKCU:\\\\Software\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\BackgroundAccessApplications\",\n \"Name\": \"GlobalUserDisabled\",\n \"Value\": \"1\",\n \"OriginalValue\": \"0\",\n \"Type\": \"DWord\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableBGapps\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableLMS1/","title":"Disable Intel MM (vPro LMS)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Intel LMS service is always listening on all ports and could be a huge security risk. There is no need to run LMS on home machines and even in the Enterprise there are better solutions.
Preview Code
{\n \"Content\": \"Disable Intel MM (vPro LMS)\",\n \"Description\": \"Intel LMS service is always listening on all ports and could be a huge security risk. There is no need to run LMS on home machines and even in the Enterprise there are better solutions.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a026_\",\n \"InvokeScript\": [\n \"\n Write-Host \\\"Kill LMS\\\"\n $serviceName = \\\"LMS\\\"\n Write-Host \\\"Stopping and disabling service: $serviceName\\\"\n Stop-Service -Name $serviceName -Force -ErrorAction SilentlyContinue;\n Set-Service -Name $serviceName -StartupType Disabled -ErrorAction SilentlyContinue;\n\n Write-Host \\\"Removing service: $serviceName\\\";\n sc.exe delete $serviceName;\n\n Write-Host \\\"Removing LMS driver packages\\\";\n $lmsDriverPackages = Get-ChildItem -Path \\\"C:\\\\Windows\\\\System32\\\\DriverStore\\\\FileRepository\\\" -Recurse -Filter \\\"lms.inf*\\\";\n foreach ($package in $lmsDriverPackages) {\n Write-Host \\\"Removing driver package: $($package.Name)\\\";\n pnputil /delete-driver $($package.Name) /uninstall /force;\n }\n if ($lmsDriverPackages.Count -eq 0) {\n Write-Host \\\"No LMS driver packages found in the driver store.\\\";\n } else {\n Write-Host \\\"All found LMS driver packages have been removed.\\\";\n }\n\n Write-Host \\\"Searching and deleting LMS executable files\\\";\n $programFilesDirs = @(\\\"C:\\\\Program Files\\\", \\\"C:\\\\Program Files (x86)\\\");\n $lmsFiles = @();\n foreach ($dir in $programFilesDirs) {\n $lmsFiles += Get-ChildItem -Path $dir -Recurse -Filter \\\"LMS.exe\\\" -ErrorAction SilentlyContinue;\n }\n foreach ($file in $lmsFiles) {\n Write-Host \\\"Taking ownership of file: $($file.FullName)\\\";\n & icacls $($file.FullName) /grant Administrators:F /T /C /Q;\n & takeown /F $($file.FullName) /A /R /D Y;\n Write-Host \\\"Deleting file: $($file.FullName)\\\";\n Remove-Item $($file.FullName) -Force -ErrorAction SilentlyContinue;\n }\n if ($lmsFiles.Count -eq 0) {\n Write-Host \\\"No LMS.exe files found in Program Files directories.\\\";\n } else {\n Write-Host \\\"All found LMS.exe files have been deleted.\\\";\n }\n Write-Host 'Intel LMS vPro service has been disabled, removed, and blocked.';\n \"\n ],\n \"UndoScript\": [\n \"\n Write-Host \\\"LMS vPro needs to be redownloaded from intel.com\\\"\n\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableLMS1\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/Display/","title":"Set Display for Performance","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFOOSU {\n <#\n .SYNOPSIS\n Downloads and runs OO Shutup 10\n #>\n try {\n $OOSU_filepath = \"$ENV:temp\\OOSU10.exe\"\n $Initial_ProgressPreference = $ProgressPreference\n $ProgressPreference = \"SilentlyContinue\" # Disables the Progress Bar to drasticly speed up Invoke-WebRequest\n Invoke-WebRequest -Uri \"https://dl5.oo-software.com/files/ooshutup10/OOSU10.exe\" -OutFile $OOSU_filepath\n Write-Host \"Starting OO Shutup 10 ...\"\n Start-Process $OOSU_filepath\n } catch {\n Write-Host \"Error Downloading and Running OO Shutup 10\" -ForegroundColor Red\n }\n finally {\n $ProgressPreference = $Initial_ProgressPreference\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveCopilot/","title":"Disable Microsoft Copilot","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveEdge/","title":"Remove Microsoft Edge","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Uninstall-WinUtilEdgeBrowser {\n\n <#\n\n .SYNOPSIS\n This will uninstall edge by changing the region to Ireland and uninstalling edge the changing it back\n\n #>\n\n$msedgeProcess = Get-Process -Name \"msedge\" -ErrorAction SilentlyContinue\n$widgetsProcess = Get-Process -Name \"widgets\" -ErrorAction SilentlyContinue\n# Checking if Microsoft Edge is running\nif ($msedgeProcess) {\n Stop-Process -Name \"msedge\" -Force\n} else {\n Write-Output \"msedge process is not running.\"\n}\n# Checking if Widgets is running\nif ($widgetsProcess) {\n Stop-Process -Name \"widgets\" -Force\n} else {\n Write-Output \"widgets process is not running.\"\n}\n\nfunction Uninstall-Process {\n param (\n [Parameter(Mandatory = $true)]\n [string]$Key\n )\n\n $originalNation = [microsoft.win32.registry]::GetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', [Microsoft.Win32.RegistryValueKind]::String)\n\n # Set Nation to 84 (France) temporarily\n [microsoft.win32.registry]::SetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', 68, [Microsoft.Win32.RegistryValueKind]::String) | Out-Null\n\n # credits to he3als for the Acl commands\n $fileName = \"IntegratedServicesRegionPolicySet.json\"\n $pathISRPS = [Environment]::SystemDirectory + \"\\\" + $fileName\n $aclISRPS = Get-Acl -Path $pathISRPS\n $aclISRPSBackup = [System.Security.AccessControl.FileSecurity]::new()\n $aclISRPSBackup.SetSecurityDescriptorSddlForm($acl.Sddl)\n if (Test-Path -Path $pathISRPS) {\n try {\n $admin = [System.Security.Principal.NTAccount]$(New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-544')).Translate([System.Security.Principal.NTAccount]).Value\n\n $aclISRPS.SetOwner($admin)\n $rule = New-Object System.Security.AccessControl.FileSystemAccessRule($admin, 'FullControl', 'Allow')\n $aclISRPS.AddAccessRule($rule)\n Set-Acl -Path $pathISRPS -AclObject $aclISRPS\n\n Rename-Item -Path $pathISRPS -NewName ($fileName + '.bak') -Force\n }\n catch {\n Write-Error \"[$Mode] Failed to set owner for $pathISRPS\"\n }\n }\n\n $baseKey = 'HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdate'\n $registryPath = $baseKey + '\\ClientState\\' + $Key\n\n if (!(Test-Path -Path $registryPath)) {\n Write-Host \"[$Mode] Registry key not found: $registryPath\"\n return\n }\n\n Remove-ItemProperty -Path $registryPath -Name \"experiment_control_labels\" -ErrorAction SilentlyContinue | Out-Null\n\n $uninstallString = (Get-ItemProperty -Path $registryPath).UninstallString\n $uninstallArguments = (Get-ItemProperty -Path $registryPath).UninstallArguments\n\n if ([string]::IsNullOrEmpty($uninstallString) -or [string]::IsNullOrEmpty($uninstallArguments)) {\n Write-Host \"[$Mode] Cannot find uninstall methods for $Mode\"\n return\n }\n\n $uninstallArguments += \" --force-uninstall --delete-profile\"\n\n # $uninstallCommand = \"`\"$uninstallString`\"\" + $uninstallArguments\n if (!(Test-Path -Path $uninstallString)) {\n Write-Host \"[$Mode] setup.exe not found at: $uninstallString\"\n return\n }\n Start-Process -FilePath $uninstallString -ArgumentList $uninstallArguments -Wait -NoNewWindow -Verbose\n\n # Restore Acl\n if (Test-Path -Path ($pathISRPS + '.bak')) {\n Rename-Item -Path ($pathISRPS + '.bak') -NewName $fileName -Force\n Set-Acl -Path $pathISRPS -AclObject $aclISRPSBackup\n }\n\n # Restore Nation\n [microsoft.win32.registry]::SetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', $originalNation, [Microsoft.Win32.RegistryValueKind]::String) | Out-Null\n\n if ((Get-ItemProperty -Path $baseKey).IsEdgeStableUninstalled -eq 1) {\n Write-Host \"[$Mode] Edge Stable has been successfully uninstalled\"\n }\n}\n\nfunction Uninstall-Edge {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft Edge\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n [microsoft.win32.registry]::SetValue(\"HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdateDev\", \"AllowUninstall\", 1, [Microsoft.Win32.RegistryValueKind]::DWord) | Out-Null\n\n Uninstall-Process -Key '{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}'\n\n @( \"$env:ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\",\n \"$env:PUBLIC\\Desktop\",\n \"$env:USERPROFILE\\Desktop\" ) | ForEach-Object {\n $shortcutPath = Join-Path -Path $_ -ChildPath \"Microsoft Edge.lnk\"\n if (Test-Path -Path $shortcutPath) {\n Remove-Item -Path $shortcutPath -Force\n }\n }\n\n}\n\nfunction Uninstall-WebView {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft EdgeWebView\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n # Force to use system-wide WebView2\n # [microsoft.win32.registry]::SetValue(\"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Edge\\WebView2\\BrowserExecutableFolder\", \"*\", \"%%SystemRoot%%\\System32\\Microsoft-Edge-WebView\")\n\n Uninstall-Process -Key '{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}'\n}\n\nfunction Uninstall-EdgeUpdate {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft Edge Update\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n $registryPath = 'HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdate'\n if (!(Test-Path -Path $registryPath)) {\n Write-Host \"Registry key not found: $registryPath\"\n return\n }\n $uninstallCmdLine = (Get-ItemProperty -Path $registryPath).UninstallCmdLine\n\n if ([string]::IsNullOrEmpty($uninstallCmdLine)) {\n Write-Host \"Cannot find uninstall methods for $Mode\"\n return\n }\n\n Write-Output \"Uninstalling: $uninstallCmdLine\"\n Start-Process cmd.exe \"/c $uninstallCmdLine\" -WindowStyle Hidden -Wait\n}\n\nUninstall-Edge\n # \"WebView\" { Uninstall-WebView }\n # \"EdgeUpdate\" { Uninstall-EdgeUpdate }\n\n\n\n\n}\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveHomeGallery/","title":"Remove Home and Gallery from explorer","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Great Windows 11 tweak to bring back good context menus when right clicking things in explorer.
Preview Code
{\n \"Content\": \"Set Classic Right-Click Menu \",\n \"Description\": \"Great Windows 11 tweak to bring back good context menus when right clicking things in explorer.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a027_\",\n \"InvokeScript\": [\n \"\n New-Item -Path \\\"HKCU:\\\\Software\\\\Classes\\\\CLSID\\\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\\\" -Name \\\"InprocServer32\\\" -force -value \\\"\\\"\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \\\"explorer\\\"\n Stop-Process -InputObject $process\n \"\n ],\n \"UndoScript\": [\n \"\n Remove-Item -Path \\\"HKCU:\\\\Software\\\\Classes\\\\CLSID\\\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\\\" -Recurse -Confirm:$false -Force\n # Restarting Explorer in the Undo Script might not be necessary, as the Registry change without restarting Explorer does work, but just to make sure.\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \\\"explorer\\\"\n Stop-Process -InputObject $process\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/RightClickMenu\"\n}\n
Remove-Item -Path \"HKCU:\\Software\\Classes\\CLSID\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\" -Recurse -Confirm:$false -Force\n # Restarting Explorer in the Undo Script might not be necessary, as the Registry change without restarting Explorer does work, but just to make sure.\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \"explorer\"\n Stop-Process -InputObject $process\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/UTC/","title":"Set Time to UTC (Dual Boot)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Essential for computers that are dual booting. Fixes the time sync with Linux Systems.
Preview Code
{\n \"Content\": \"Set Time to UTC (Dual Boot)\",\n \"Description\": \"Essential for computers that are dual booting. Fixes the time sync with Linux Systems.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a027_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\TimeZoneInformation\",\n \"Name\": \"RealTimeIsUniversal\",\n \"Type\": \"DWord\",\n \"Value\": \"1\",\n \"OriginalValue\": \"0\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/UTC\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to the WinUtil Documentation!","text":"
Welcome to the official documentation for WinUtil, your go-to utility for optimizing and managing your Windows environment. Whether you\u2019re an IT professional, power user, or regular user, WinUtil provides a comprehensive set of tools to enhance your Windows experience.
"},{"location":"#running-the-latest-release-of-winutil","title":"Running the latest release of WinUtil","text":"
You will first need to start a Powershell terminal as Admin.
Now you can run the following command:
irm christitus.com/win | iex\n
Info
WinUtil is updated weekly as of the time of writing. Consequently, features and functionalities may evolve, and the documentation may not always reflect the most current images or information.
Windows Security (formerly Defender) and other anti-virus software are known to block the script. The script gets flagged due to the fact that it requires administrator privileges & makes drastic system changes.
If possible: Allow script in Anti-Virus software settings.
If you are having TLS 1.2 issues, or are having trouble resolving christitus.com/win then run with the following command:
If you are unable to resolve christitus.com/win and are getting errors launching the tool, it might be due to India blocking GitHub's content domain and preventing downloads.
#69 Turn on fast startup: Press Windows key + R, then type:
control /name Microsoft.PowerOptions /page pageGlobalSettings\n
If that doesn't work, Disable Hibernation: Press Windows Key+X and select 'PowerShell (Admin)' (Windows 10) or 'Windows Terminal (Admin)' (Windows 11) and enter:
powercfg /H off\n
#69 95 #232 Windows Search does not work: Enable Background Apps
#198 Xbox Game Bar Activation Broken: Set the Xbox Accessory Management Service to Automatic
Open the generated HTML report to identify energy consumption patterns.
Review Event Viewer:
Open Event Viewer by searching for it in the Start menu.
Navigate to \"Windows Logs\" > \"System.\"
Look for events with the source \"Power-Troubleshooter\" to identify power-related events.
Check Wake-up Sources:
Open a Command Prompt as an administrator.
Use the command powercfg /requests to identify processes preventing sleep.
Check Task Scheduler for tasks waking up the computer.
Use the command powercfg /waketimers to view active wake timers.
Resource Monitor:
Open Resource Monitor from the Start menu.
Navigate to the \"CPU\" tab and identify processes with high CPU usage.
Windows Settings - Activity History:
In \"Settings,\" go to \"Privacy\" > \"Activity history.\"
Turn off \"Let Windows collect my activities from this PC.\"
Network Adapters:
Open Device Manager by searching for it in the Start menu.
Locate your network adapter, right-click, and go to \"Properties.\"
Under the \"Power Management\" tab, uncheck the option that allows the device to wake the computer.
Review Installed Applications:
Manually review installed applications by searching for \"Add or remove programs\" in the Start menu.
Check settings/preferences of individual applications for power-related options.
Uninstall unnecessary or problematic software.
By following these detailed instructions, you should be able to thoroughly diagnose and address battery drain issues on your Windows laptop. Adjust settings as needed to optimize power management and improve battery life.
"},{"location":"KnownIssues/#troubleshoot-errors-during-microwin-usage","title":"Troubleshoot errors during Microwin usage","text":""},{"location":"KnownIssues/#error-0x80041031","title":"Error 0x80041031","text":"
This error code typically indicates an issue related to Windows Management Instrumentation (WMI). Here are a few steps you can try to resolve the issue:
Reboot Your Computer: Sometimes, a simple reboot can resolve temporary issues. Restart your computer and try mounting the ISO again.
Check for System Corruption: Run the System File Checker (SFC) utility to scan and repair system files that may be corrupted.
sfc /scannow\n
Update Your System: Make sure your operating system is up-to-date. Check for Windows updates and install any pending updates.
Check WMI Service: Ensure that the Windows Management Instrumentation (WMI) service is running. You can do this through the Services application:
Press Win + R to open the Run dialog.
Type services.msc and press Enter.
Locate \"Windows Management Instrumentation\" in the list.
Make sure to set its status to \"Running\" and the startup type to \"Automatic.\"
Check for Security Software Interference: Security software can sometimes interfere with WMI operations. Temporarily disable your antivirus or security software and check if the issue persists.
Event Viewer: Check the Event Viewer for more detailed error information. Look for entries related to the 80041031 error and check if there are any additional details that can help identify the cause.
Press Win + X and select \"Event Viewer.\"
Navigate to \"Windows Logs\" -> \"Application\" or \"System.\"
Look for entries with the source related to WMI or the application use to mount the ISO.
ISO File Integrity: Ensure that the ISO file you are trying to mount is uncorrupted. Try mounting a different ISO file to see if the issue persists.
If the problem persists after trying these steps, additional troubleshooting is required. Consider seeking assistance from Microsoft support or community forums for more specific guidance based on your system configuration and the software you use to mount the ISO.
"},{"location":"contribute/","title":"How to Contribute?","text":""},{"location":"contribute/#testing","title":"Testing","text":"
Test the latest changes to WinUtil by running the pre-release and reporting issues you are encountering to help us continually improve WinUtil!
"},{"location":"contribute/#run-the-latest-pre-release","title":"Run the latest pre-release","text":"
irm christitus.com/windev | iex\n
Keep in mind
This is a pre-release and should be treated as such. It exists for developers to test the utility and report or fix bugs before they get added to the stable release. Don't use it in production!
If you encounter any challenges or problems with the script, I kindly request that you submit them via the \"Issues\" tab on the GitHub repository. By filling out the provided template, you can provide specific details about the issue, allowing me (and others in the community) to promptly address any bugs or consider feature requests.
Pull requests are now handled directly on the MAIN branch. This was done since we can now select specific releases to launch via releases in GitHub.
If you're doing code changes, then you can submit a PR to main branch, but I am very selective about these.
Important
Do not use a code formatter, make massive amounts of line changes, or make multiple feature changes. EACH FEATURE CHANGE SHOULD BE IT'S OWN PULL REQUEST!
When creating pull requests, it is essential to thoroughly document all changes made. This includes, but is not limited to, documenting any additions made to the tweaks section and corresponding undo tweak, so users are able to remove the newly added tweaks if necessary, and comprehensive documentation is required for all code changes. Document your changes and briefly explain why you made your changes in your Pull Request Description. Failure to adhere to this format may result in the denial of the pull request. Additionally, any code lacking sufficient documentation may also be denied.
By following these guidelines, we can maintain a high standard of quality and ensure that the codebase remains organized and well-documented.
Note
When creating a function, please include \"WPF\" or \"WinUtil\" in the file name so it can be loaded into the runspace.
%%{init: {\"flowchart\": {\"curve\": \"cardinal\"}} }%%\ngraph TD\n\u00a0 A[Fork Project] --> B[Clone Repository];\n\u00a0 B --> C[Create New Branch];\n\u00a0 C --> D[Make Changes];\n\u00a0 D --> G[Test Changes];\n\u00a0 G --> H{Tests Passed?};\n\u00a0 H -->|Yes| E[Commit Changes];\n\u00a0 H -->|No| J[Fix Issues];\n\u00a0 J --> G;\n\u00a0 E --> F[Push Branch];\n\u00a0 F --> K[Create Pull Request];\n\u00a0 K --> L[Fill out PR template];\n classDef default stroke:#333,stroke-width:4px,font-size:12pt;
Info
This is a diagram to guide you through the process. It may vary depending on the type of change you're making.
"},{"location":"contribute/#fork-the-repo","title":"Fork the Repo","text":"
Fork the WinUtil Repository here to create a copy that will be available in your repository list.
"},{"location":"contribute/#clone-the-fork","title":"Clone the Fork","text":"
Tip
While you can make your changes directly through the Web, we recommend cloning the repo to your device using the application GitHub Desktop (available in WinUtil) to test your fork easily.
Install GitHub Desktop if it is not already installed.
Log in using the same GitHub account you used to fork WinUtil.
Choose the fork under \"Your Repositories\" and press \"clone {repo name}\"
Create a new branch and name it something relatable to your changes.
Now you can modify WinUtil to your liking using your preferred text editor.
"},{"location":"contribute/#testing-your-changes","title":"Testing your changes","text":"
To test to see if your changes work as intended run following commands in a powershell teminal as admin:
Change the directory where you are running the commands to the forked project.
cd {path to the folder with the compile.ps1}
Run the following command to compile and run WinUtil:
.\\Compile.ps1 -run
After seeing that your changes work properly, feel free to commit the changes to the repository and make a PR. For help on that, follow the documentation below.
"},{"location":"contribute/#committing-the-changes","title":"Committing the changes","text":"
Before committing your changes, please discard changes made to the winutil.ps1 file, like the following:
Now, commit your changes once you are happy with the result.
Push the changes to upload them to your fork on github.com.
"},{"location":"contribute/#making-a-pr","title":"Making a PR","text":"
To make a PR on your repo under a new branch linking to the main branch, a button will show and say Preview and Create pull request. Click that button and fill in all the information that is provided on the template. Once all the information is filled in correctly, check your PR to make sure there is not a WinUtil.ps1 file attached to the PR. Once everything is good, make the PR and wait for Chris (the maintainer) to accept or deny your PR. Once it is accepted by Chris, you will be able to see your changes in the \"/windev\" build.
If you do not see your feature in the main \"/win\" build, that is fine. All new changes go into the /windev build to make sure everything is working OK before going fully public.
Congratulations! You just submitted your first PR. Thank you so much for contributing to WinUtil.
"},{"location":"devdocs/","title":"Table of Contents","text":""},{"location":"devdocs/#tweaks","title":"Tweaks","text":""},{"location":"devdocs/#z-advanced-tweaks-caution","title":"z--Advanced-Tweaks---CAUTION","text":"
Disable Search Box Web Suggestions in Registry(explorer restart)
Enable Daily Registry Backup Task 12.30am
Enable Legacy F8 Boot Recovery
Enable Search Box Web Suggestions in Registry(explorer restart)
HyperV Virtualization
Install Features
Legacy Media (WMP, DirectPlay)
NFS - Network File System
Windows Sandbox
Windows Subsystem for Linux
"},{"location":"faq/","title":"FAQ's","text":""},{"location":"faq/#how-do-i-uninstall-winutil","title":"How do I uninstall WinUtil?","text":"
You do not have to uninstall WinUtil. As it is a script you run from Powershell it only loads into your RAM. This means as soon as you close WinUtil it will be deleted off your system.
"},{"location":"faq/#i-applied-a-tweak-and-now-something-doesnt-work-what-do-i-do","title":"I applied a tweak and now something doesn't work, what do I do?","text":"
If you applied a tweak and it breaks something, you can always revert the tweak by selecting the tweak and clicking \"Undo Selected Tweaks\".
Essential Tweaks are modifications and optimizations that are generally safe for most users to implement. These tweaks are designed to enhance system performance, improve privacy, and reduce unnecessary system activities. They are considered low-risk and are recommended for users who want to ensure their system runs smoothly and efficiently without delving too deeply into complex configurations. The goal of Essential Tweaks is to provide noticeable improvements with minimal risk, making them suitable for a wide range of users, including those who may not have advanced technical knowledge.
Advanced Tweaks are intended for experienced users who have a solid understanding of their system and the potential implications of making deep-level changes. These tweaks involve more significant alterations to the operating system and can provide substantial customization. However, they also carry a higher risk of causing system instability or unintended side effects if not implemented correctly. Users who choose to apply Advanced Tweaks should proceed with caution, ensuring they have adequate knowledge and backups in place to recover if something goes wrong. These tweaks are not recommended for novice users or those unfamiliar with the inner workings of their operating system.
O&O ShutUp10++ can be launched from WinUtil with only one button click. It is a free privacy tool for Windows that lets users easily manage their privacy settings. It disables telemetry, controls updates, and manages app permissions to enhance security and privacy. The tool offers recommended settings for optimal privacy with just a few clicks.
The utility provides a convenient DNS selection feature, allowing users to choose between various DNS providers for both IPv4 and IPv6. This enables users to optimize their internet connection for speed, security, and privacy according to their specific needs. Here are the available options:
Default: Uses the default DNS settings configured by your ISP or network.
DHCP: Automatically acquires DNS settings from the DHCP server.
Google: A reliable and fast DNS service provided by Google.
Cloudflare: Known for speed and privacy, Cloudflare DNS is a popular choice for enhancing internet performance.
Cloudflare_Malware: Provides additional protection by blocking malware sites.
Cloudflare_Malware_Adult: Blocks both malware and adult content, offering more comprehensive filtering.
Level3: Another fast and reliable DNS service option.
Open_DNS: Offers customizable filtering and enhanced security features.
Quad9: Focuses on security by blocking known malicious domains.
The Customize Preferences section allows users to personalize their Windows experience by toggling various visual and functional features. These preferences are designed to enhance usability and tailor the system to the user\u2019s specific needs and preferences.
The Performance Plans section allows users to manage the Ultimate Performance Profile on their system. This feature is designed to optimize the system for maximum performance.
"},{"location":"userguide/#add-and-activate-the-ultimate-performance-profile","title":"Add and activate the Ultimate Performance Profile:","text":"
Enables and activates the Ultimate Performance Profile to enhance system performance by minimizing latency and increasing efficiency.
The utility provides three distinct settings for managing Windows updates: Default (Out of Box) Settings, Security (Recommended) Settings, and Disable ALL Updates (NOT RECOMMENDED!). Each setting offers a different approach to handling updates, catering to various user needs and preferences.
"},{"location":"userguide/#default-out-of-box-settings","title":"Default (Out of Box) Settings","text":"
Description: This setting retains the default configurations that come with Windows, ensuring no modifications are made.
Functionality: It will remove any custom Windows update settings previously applied.
Note: If update errors persist, reset all updates in the configuration tab to restore all Microsoft Update Services to their default settings, reinstalling them from their servers.
Description: This is the recommended setting for all computers.
Update Schedule:
Feature Updates: Delays feature updates by 2 years to avoid potential bugs and instability.
Security Updates: Installs security updates 4 days after their release to ensure system protection against pressing security flaws.
Rationale:
Feature Updates: Often introduce new features and bugs; delaying these updates minimizes the risk of system disruptions.
Security Updates: Essential for patching critical security vulnerabilities. Delaying them by a few days allows for verification of stability and compatibility without leaving the system exposed for extended periods.
"},{"location":"userguide/#disable-all-updates-not-recommended","title":"Disable ALL Updates (NOT RECOMMENDED!)","text":"
Description: This setting completely disables all Windows updates.
Suitability: May be appropriate for systems used for specific purposes that do not require active internet browsing.
Warning: Disabling updates significantly increases the risk of the system being hacked or infected due to the lack of security patches.
Note: It is strongly advised against using this setting due to the heightened security risks.
Bug
The Updates tab is currently non-functional. We are actively working on a resolution to restore its functionality.
If you don't have a Windows ISO file prepared, you can download it using the Media Creation Tool for the respective Windows version. Here is the Windows 11 version, and here is the Windows 10 version
Configure the debloat process.
Specify the target location for the new ISO file.
Let the magic happen!
Heads-up
This feature is still in development, and you may encounter some issues with the generated images. If that happens, don't hesitate to report an issue!
Download oscdimg.exe from the CTT GitHub repo will grab an OSCDIMG executable from the GitHub repository instead of a Chocolatey package.
Info
OSCDIMG is the tool that lets the program create ISO images. Typically, you would find this in the Windows Assessment and Deployment Kit
Selecting a scratch directory will copy the contents of the ISO file to the directory you specify instead of an automatically generated folder in the %TEMP% directory.
You can select an edition of Windows to debloat (SKU) using the convenient drop-down menu.
By default, MicroWin will debloat the Pro edition, but you can choose any edition you want.
Inject drivers will add the drivers in the folder that you specify to the target Windows image.
Import drivers from the current system will add every third-party driver that is present in your active installation.
This makes the target image have the same hardware compatibility as the active installation. However, this means that you will only be able to install the target Windows image and take full advantage of it on computers with the same hardware. To avoid this, you'll need to customize the install.wim file of the target ISO in the 'sources` folder.
"},{"location":"userguide/#custom-user-settings","title":"Custom user settings","text":"
With MicroWin, you can also configure your user before proceeding if you don't want to use the default User account. To do this, simply type the account name (20 characters maximum), and a password. Then, let MicroWin do the rest.
Info
Please make sure that you remember your password. MicroWin will configure auto-login settings, so you won't have to enter your password. However, if you are required to enter your password, it's best that you don't forget it.
Copy to Ventoy will copy the target ISO file to any USB drive with Ventoy installed
Info
Ventoy is a solution that lets you boot to any ISO file stored on a drive. Think of it as having multiple bootable USBs in one. Do note, though, that your drive needs to have enough free space for the target ISO file.
Some features are available through automation. This allows you to save your config file, pass it to WinUtil, walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
On the Install Tab, click \"Get Installed\", this will get all installed apps supported by Winutil on the system.
Click on the Settings cog in the upper right corner and choose Export. Choose file file and location; this will export the setting file.
Copy this file to a USB or somewhere you can use it after Windows installation.
Tip
Use the Microwin tab to create a custom Windows image & install the Windows image.
On any supported Windows machine, open PowerShell as Admin and run the following command to automatically apply tweaks and install apps from the config file.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/features/Features/DisableSearchSuggestions/","title":"Disable Search Box Web Suggestions in Registry(explorer restart)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/features/Features/EnableSearchSuggestions/","title":"Enable Search Box Web Suggestions in Registry(explorer restart)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows Sandbox is a lightweight virtual machine that provides a temporary desktop environment to safely run applications and programs in isolation.
Preview Code
{\n \"Content\": \"Windows Sandbox\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a021_\",\n \"Description\": \"Windows Sandbox is a lightweight virtual machine that provides a temporary desktop environment to safely run applications and programs in isolation.\",\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/Sandbox\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
.NET and .NET Framework is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
Preview Code
{\n \"Content\": \"All .Net Framework (2,3,4)\",\n \"Description\": \".NET and .NET Framework is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a010_\",\n \"feature\": [\n \"NetFx4-AdvSrvs\",\n \"NetFx3\"\n ],\n \"InvokeScript\": [],\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/dotnet\"\n}\n
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/dotnet/#features-to-install","title":"Features to install","text":"
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/hyperv/#features-to-install","title":"Features to install","text":"
"},{"location":"dev/features/Features/legacymedia/","title":"Legacy Media (WMP, DirectPlay)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/legacymedia/#features-to-install","title":"Features to install","text":"
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/nfs/#features-to-install","title":"Features to install","text":"
"},{"location":"dev/features/Features/wsl/","title":"Windows Subsystem for Linux","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows Subsystem for Linux is an optional feature of Windows that allows Linux programs to run natively on Windows without the need for a separate virtual machine or dual booting.
Preview Code
{\n \"Content\": \"Windows Subsystem for Linux\",\n \"Description\": \"Windows Subsystem for Linux is an optional feature of Windows that allows Linux programs to run natively on Windows without the need for a separate virtual machine or dual booting.\",\n \"category\": \"Features\",\n \"panel\": \"1\",\n \"Order\": \"a020_\",\n \"feature\": [\n \"VirtualMachinePlatform\",\n \"Microsoft-Windows-Subsystem-Linux\"\n ],\n \"InvokeScript\": [],\n \"link\": \"https://christitustech.github.io/winutil/dev/features/Features/wsl\"\n}\n
Optional Windows Features are additional functionalities or components in the Windows operating system that users can choose to enable or disable based on their specific needs and preferences.
You can find information about Optional Windows Features on Microsoft's Website for Optional Features.
"},{"location":"dev/features/Features/wsl/#features-to-install","title":"Features to install","text":"
VirtualMachinePlatform
Microsoft-Windows-Subsystem-Linux
View the JSON file
"},{"location":"dev/features/Fixes/Autologin/","title":"Set Up Autologin","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFPanelDISM {\n <#\n\n .SYNOPSIS\n Checks for system corruption using Chkdsk, SFC, and DISM\n\n .DESCRIPTION\n 1. Chkdsk - Fixes disk and filesystem corruption\n 2. SFC Run 1 - Fixes system file corruption, and fixes DISM if it was corrupted\n 3. DISM - Fixes system image corruption, and fixes SFC's system image if it was corrupted\n 4. SFC Run 2 - Fixes system file corruption, this time with an almost guaranteed uncorrupted system image\n\n .NOTES\n Command Arguments:\n 1. Chkdsk\n /Scan - Runs an online scan on the system drive, attempts to fix any corruption, and queues other corruption for fixing on reboot\n 2. SFC\n /ScanNow - Performs a scan of the system files and fixes any corruption\n 3. DISM - Fixes system image corruption, and fixes SFC's system image if it was corrupted\n /Online - Fixes the currently running system image\n /Cleanup-Image - Performs cleanup operations on the image, could remove some unneeded temporary files\n /Restorehealth - Performs a scan of the image and fixes any corruption\n\n #>\n Start-Process PowerShell -ArgumentList \"Write-Host '(1/4) Chkdsk' -ForegroundColor Green; Chkdsk /scan;\n Write-Host '`n(2/4) SFC - 1st scan' -ForegroundColor Green; sfc /scannow;\n Write-Host '`n(3/4) DISM' -ForegroundColor Green; DISM /Online /Cleanup-Image /Restorehealth;\n Write-Host '`n(4/4) SFC - 2nd scan' -ForegroundColor Green; sfc /scannow;\n Read-Host '`nPress Enter to Continue'\" -verb runas\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFRunAdobeCCCleanerTool {\n <#\n .SYNOPSIS\n It removes or fixes problem files and resolves permission issues in registry keys.\n .DESCRIPTION\n The Creative Cloud Cleaner tool is a utility for experienced users to clean up corrupted installations.\n #>\n\n [string]$url=\"https://swupmf.adobe.com/webfeed/CleanerTool/win/AdobeCreativeCloudCleanerTool.exe\"\n\n Write-Host \"The Adobe Creative Cloud Cleaner tool is hosted at\"\n Write-Host \"$url\"\n\n try {\n # Don't show the progress because it will slow down the download speed\n $ProgressPreference='SilentlyContinue'\n\n Invoke-WebRequest -Uri $url -OutFile \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -UseBasicParsing -ErrorAction SilentlyContinue -Verbose\n\n # Revert back the ProgressPreference variable to the default value since we got the file desired\n $ProgressPreference='Continue'\n\n Start-Process -FilePath \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -Wait -ErrorAction SilentlyContinue -Verbose\n } catch {\n Write-Error $_.Exception.Message\n } finally {\n if (Test-Path -Path \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\") {\n Write-Host \"Cleaning up...\"\n Remove-Item -Path \"$env:TEMP\\AdobeCreativeCloudCleanerTool.exe\" -Verbose\n }\n }\n}\n
View the JSON file
"},{"location":"dev/features/Fixes/Update/","title":"Reset Windows Update","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFFixesWinget {\n\n <#\n\n .SYNOPSIS\n Fixes Winget by running choco install winget\n .DESCRIPTION\n BravoNorris for the fantastic idea of a button to reinstall winget\n #>\n # Install Choco if not already present\n Install-WinUtilChoco\n Start-Process -FilePath \"choco\" -ArgumentList \"install winget -y --force\" -NoNewWindow -Wait\n\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/tweaks/Customize-Preferences/BingSearch/","title":"Bing Search in Start Menu","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If enable then includes web search results from Bing in your Start Menu search.
Preview Code
{\n \"Content\": \"Bing Search in Start Menu\",\n \"Description\": \"If enable then includes web search results from Bing in your Start Menu search.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a101_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/BingSearch\"\n}\n
function Invoke-WinUtilBingSearch {\n <#\n\n .SYNOPSIS\n Disables/Enables Bing Search\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Bing Search\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Bing Search\"\n $value = 1\n } else {\n Write-Host \"Disabling Bing Search\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Search\"\n Set-ItemProperty -Path $Path -Name BingSearchEnabled -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/DarkMode/","title":"Dark Theme for Windows","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then you will see a detailed Blue Screen of Death (BSOD) with more information.
Preview Code
{\n \"Content\": \"Detailed BSoD\",\n \"Description\": \"If Enabled then you will see a detailed Blue Screen of Death (BSOD) with more information.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a205_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/DetailedBSoD\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then Cursor movement is affected by the speed of your physical mouse movements.
Preview Code
{\n \"Content\": \"Mouse Acceleration\",\n \"Description\": \"If Enabled then Cursor movement is affected by the speed of your physical mouse movements.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a107_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/MouseAcceleration\"\n}\n
Function Invoke-WinUtilMouseAcceleration {\n <#\n\n .SYNOPSIS\n Enables/Disables Mouse Acceleration\n\n .PARAMETER DarkMoveEnabled\n Indicates the current Mouse Acceleration State\n\n #>\n Param($MouseAccelerationEnabled)\n try {\n if ($MouseAccelerationEnabled -eq $false) {\n Write-Host \"Enabling Mouse Acceleration\"\n $MouseSpeed = 1\n $MouseThreshold1 = 6\n $MouseThreshold2 = 10\n } else {\n Write-Host \"Disabling Mouse Acceleration\"\n $MouseSpeed = 0\n $MouseThreshold1 = 0\n $MouseThreshold2 = 0\n\n }\n\n $Path = \"HKCU:\\Control Panel\\Mouse\"\n Set-ItemProperty -Path $Path -Name MouseSpeed -Value $MouseSpeed\n Set-ItemProperty -Path $Path -Name MouseThreshold1 -Value $MouseThreshold1\n Set-ItemProperty -Path $Path -Name MouseThreshold2 -Value $MouseThreshold2\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/NumLock/","title":"NumLock on Startup","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Toggle the Num Lock key state when your computer starts.
Preview Code
{\n \"Content\": \"NumLock on Startup\",\n \"Description\": \"Toggle the Num Lock key state when your computer starts.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a102_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/NumLock\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If enabled then you will get suggestions to snap other applications in the left over spaces.
Preview Code
{\n \"Content\": \"Snap Assist Suggestion\",\n \"Description\": \"If enabled then you will get suggestions to snap other applications in the left over spaces.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a106_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/SnapSuggestion\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilSnapWindow {\n <#\n .SYNOPSIS\n Disables/Enables Snapping Windows on startup\n .PARAMETER Enabled\n Indicates whether to enable or disable Snapping Windows on startup\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Snap Windows On startup | Relogin Required\"\n $value = 1\n } else {\n Write-Host \"Disabling Snap Windows On startup | Relogin Required\"\n $value = 0\n }\n $Path = \"HKCU:\\Control Panel\\Desktop\"\n Set-ItemProperty -Path $Path -Name WindowArrangementActive -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
If Enabled then Sticky Keys is activated - Sticky keys is an accessibility feature of some graphical user interfaces which assists users who have physical disabilities or help users reduce repetitive strain injury.
Preview Code
{\n \"Content\": \"Sticky Keys\",\n \"Description\": \"If Enabled then Sticky Keys is activated - Sticky keys is an accessibility feature of some graphical user interfaces which assists users who have physical disabilities or help users reduce repetitive strain injury.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a108_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/StickyKeys\"\n}\n
Function Invoke-WinUtilStickyKeys {\n <#\n .SYNOPSIS\n Disables/Enables Sticky Keyss on startup\n .PARAMETER Enabled\n Indicates whether to enable or disable Sticky Keys on startup\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Sticky Keys On startup\"\n $value = 510\n } else {\n Write-Host \"Disabling Sticky Keys On startup\"\n $value = 58\n }\n $Path = \"HKCU:\\Control Panel\\Accessibility\\StickyKeys\"\n Set-ItemProperty -Path $Path -Name Flags -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskView/","title":"Task View Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
[Windows 11] If Enabled then the Taskbar Items will be shown on the Center, otherwise the Taskbar Items will be shown on the Left.
Preview Code
{\n \"Content\": \"Center Taskbar Items\",\n \"Description\": \"[Windows 11] If Enabled then the Taskbar Items will be shown on the Center, otherwise the Taskbar Items will be shown on the Left.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a204_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/TaskbarAlignment\"\n}\n
function Invoke-WinUtilTaskbarAlignment {\n <#\n\n .SYNOPSIS\n Switches between Center & Left Taskbar Alignment\n\n .PARAMETER Enabled\n Indicates whether to make Taskbar Alignment Center or Left\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Making Taskbar Alignment to the Center\"\n $value = 1\n } else {\n Write-Host \"Making Taskbar Alignment to the Left\"\n $value = 0\n }\n $Path = \"HKCU:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced\"\n Set-ItemProperty -Path $Path -Name \"TaskbarAl\" -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskbarSearch/","title":"Search Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilTaskbarSearch {\n <#\n\n .SYNOPSIS\n Enable/Disable Taskbar Search Button.\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Taskbar Search Button.\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Search Button\"\n $value = 1\n } else {\n Write-Host \"Disabling Search Button\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Search\\\"\n Set-ItemProperty -Path $Path -Name SearchboxTaskbarMode -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/TaskbarWidgets/","title":"Widgets Button in Taskbar","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WinUtilTaskbarWidgets {\n <#\n\n .SYNOPSIS\n Enable/Disable Taskbar Widgets\n\n .PARAMETER Enabled\n Indicates whether to enable or disable Taskbar Widgets\n\n #>\n Param($Enabled)\n try {\n if ($Enabled -eq $false) {\n Write-Host \"Enabling Taskbar Widgets\"\n $value = 1\n } else {\n Write-Host \"Disabling Taskbar Widgets\"\n $value = 0\n }\n $Path = \"HKCU:\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced\"\n Set-ItemProperty -Path $Path -Name TaskbarDa -Value $value\n } catch [System.Security.SecurityException] {\n Write-Warning \"Unable to set $Path\\$Name to $Value due to a Security Exception\"\n } catch [System.Management.Automation.ItemNotFoundException] {\n Write-Warning $psitem.Exception.ErrorRecord\n } catch {\n Write-Warning \"Unable to set $Name due to unhandled exception\"\n Write-Warning $psitem.Exception.StackTrace\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/Customize-Preferences/VerboseLogon/","title":"Verbose Messages During Logon","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Show detailed messages during the login process for troubleshooting and diagnostics.
Preview Code
{\n \"Content\": \"Verbose Messages During Logon\",\n \"Description\": \"Show detailed messages during the login process for troubleshooting and diagnostics.\",\n \"category\": \"Customize Preferences\",\n \"panel\": \"2\",\n \"Order\": \"a103_\",\n \"Type\": \"Toggle\",\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Customize-Preferences/VerboseLogon\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Windows 10 will not automatically install any games, third-party apps, or application links from the Windows Store for the signed-in user. Some default Apps will be inaccessible (eg. Phone Link)
Preview Code
{\n \"Content\": \"Disable ConsumerFeatures\",\n \"Description\": \"Windows 10 will not automatically install any games, third-party apps, or application links from the Windows Store for the signed-in user. Some default Apps will be inaccessible (eg. Phone Link)\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a003_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SOFTWARE\\\\Policies\\\\Microsoft\\\\Windows\\\\CloudContent\",\n \"OriginalValue\": \"0\",\n \"Name\": \"DisableWindowsConsumerFeatures\",\n \"Value\": \"1\",\n \"Type\": \"DWord\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/ConsumerFeatures\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
"},{"location":"dev/tweaks/Essential-Tweaks/DiskCleanup/","title":"Run Disk Cleanup","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/EndTaskOnTaskbar/","title":"Enable End Task With Right Click","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Hibernation is really meant for laptops as it saves what's in memory before turning the pc off. It really should never be used, but some people are lazy and rely on it. Don't be like Bob. Bob likes hibernation.
Preview Code
{\n \"Content\": \"Disable Hibernation\",\n \"Description\": \"Hibernation is really meant for laptops as it saves what's in memory before turning the pc off. It really should never be used, but some people are lazy and rely on it. Don't be like Bob. Bob likes hibernation.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a005_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\System\\\\CurrentControlSet\\\\Control\\\\Session Manager\\\\Power\",\n \"Name\": \"HibernateEnabled\",\n \"Type\": \"DWord\",\n \"Value\": \"0\",\n \"OriginalValue\": \"1\"\n },\n {\n \"Path\": \"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Explorer\\\\FlyoutMenuSettings\",\n \"Name\": \"ShowHibernateOption\",\n \"Type\": \"DWord\",\n \"Value\": \"0\",\n \"OriginalValue\": \"1\"\n }\n ],\n \"InvokeScript\": [\n \"powercfg.exe /hibernate off\"\n ],\n \"UndoScript\": [\n \"powercfg.exe /hibernate on\"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Hiber\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Disables HomeGroup - HomeGroup is a password-protected home networking service that lets you share your stuff with other PCs that are currently running and connected to your network.
Preview Code
{\n \"Content\": \"Disable Homegroup\",\n \"Description\": \"Disables HomeGroup - HomeGroup is a password-protected home networking service that lets you share your stuff with other PCs that are currently running and connected to your network.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a005_\",\n \"service\": [\n {\n \"Name\": \"HomeGroupListener\",\n \"StartupType\": \"Manual\",\n \"OriginalType\": \"Automatic\"\n },\n {\n \"Name\": \"HomeGroupProvider\",\n \"StartupType\": \"Manual\",\n \"OriginalType\": \"Automatic\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Home\"\n}\n
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/LaptopHibernation/","title":"Set Hibernation as default (good for laptops)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Most modern laptops have connected standby enabled which drains the battery, this sets hibernation as default which will not drain the battery. See issue https://github.com/ChrisTitusTech/winutil/issues/1399
Preview Code
{\n \"Content\": \"Set Hibernation as default (good for laptops)\",\n \"Description\": \"Most modern laptops have connected standby enabled which drains the battery, this sets hibernation as default which will not drain the battery. See issue https://github.com/ChrisTitusTech/winutil/issues/1399\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a014_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\Power\\\\PowerSettings\\\\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\\\\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0\",\n \"OriginalValue\": \"1\",\n \"Name\": \"Attributes\",\n \"Value\": \"2\",\n \"Type\": \"DWord\"\n },\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\Power\\\\PowerSettings\\\\abfc2519-3608-4c2a-94ea-171b0ed546ab\\\\94ac6d29-73ce-41a6-809f-6363ba21b47e\",\n \"OriginalValue\": \"0\",\n \"Name\": \"Attributes \",\n \"Value\": \"2\",\n \"Type\": \"DWord\"\n }\n ],\n \"InvokeScript\": [\n \"\n Write-Host \\\"Turn on Hibernation\\\"\n Start-Process -FilePath powercfg -ArgumentList \\\"/hibernate on\\\" -NoNewWindow -Wait\n\n # Set hibernation as the default action\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-ac 60\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-dc 60\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-ac 10\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-dc 1\\\" -NoNewWindow -Wait\n \"\n ],\n \"UndoScript\": [\n \"\n Write-Host \\\"Turn off Hibernation\\\"\n Start-Process -FilePath powercfg -ArgumentList \\\"/hibernate off\\\" -NoNewWindow -Wait\n\n # Set standby to detault values\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-ac 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change standby-timeout-dc 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-ac 15\\\" -NoNewWindow -Wait\n Start-Process -FilePath powercfg -ArgumentList \\\"/change monitor-timeout-dc 15\\\" -NoNewWindow -Wait\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/LaptopHibernation\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Essential-Tweaks/Powershell7/","title":"Change Windows Terminal default: PowerShell 5 -> PowerShell 7","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFTweakPS7{\n <#\n .SYNOPSIS\n This will edit the config file of the Windows Terminal Replacing the Powershell 5 to Powershell 7 and install Powershell 7 if necessary\n .PARAMETER action\n PS7: Configures Powershell 7 to be the default Terminal\n PS5: Configures Powershell 5 to be the default Terminal\n #>\n param (\n [ValidateSet(\"PS7\", \"PS5\")]\n [string]$action\n )\n\n switch ($action) {\n \"PS7\"{\n if (Test-Path -Path \"$env:ProgramFiles\\PowerShell\\7\") {\n Write-Host \"Powershell 7 is already installed.\"\n } else {\n Write-Host \"Installing Powershell 7...\"\n Invoke-WinUtilWingetProgram -Action Install -Programs @(\"Microsoft.PowerShell\")\n }\n $targetTerminalName = \"PowerShell\"\n }\n \"PS5\"{\n $targetTerminalName = \"Windows PowerShell\"\n }\n }\n # Check if the Windows Terminal is installed and return if not (Prerequisite for the following code)\n if (-not (Get-Command \"wt\" -ErrorAction SilentlyContinue)) {\n Write-Host \"Windows Terminal not installed. Skipping Terminal preference\"\n return\n }\n # Check if the Windows Terminal settings.json file exists and return if not (Prereqisite for the following code)\n $settingsPath = \"$env:LOCALAPPDATA\\Packages\\Microsoft.WindowsTerminal_8wekyb3d8bbwe\\LocalState\\settings.json\"\n if (-not (Test-Path -Path $settingsPath)) {\n Write-Host \"Windows Terminal Settings file not found at $settingsPath\"\n return\n }\n\n Write-Host \"Settings file found.\"\n $settingsContent = Get-Content -Path $settingsPath | ConvertFrom-Json\n $ps7Profile = $settingsContent.profiles.list | Where-Object { $_.name -eq $targetTerminalName }\n if ($ps7Profile) {\n $settingsContent.defaultProfile = $ps7Profile.guid\n $updatedSettings = $settingsContent | ConvertTo-Json -Depth 100\n Set-Content -Path $settingsPath -Value $updatedSettings\n Write-Host \"Default profile updated to \" -NoNewline\n Write-Host \"$targetTerminalName \" -ForegroundColor White -NoNewline\n Write-Host \"using the name attribute.\"\n } else {\n Write-Host \"No PowerShell 7 profile found in Windows Terminal settings using the name attribute.\"\n }\n}\n
Function Invoke-WinUtilWingetProgram {\n <#\n .SYNOPSIS\n Runs the designated action on the provided programs using Winget\n\n .PARAMETER Programs\n A list of programs to process\n\n .PARAMETER action\n The action to perform on the programs, can be either 'Install' or 'Uninstall'\n\n .NOTES\n The triple quotes are required any time you need a \" in a normal script block.\n The winget Return codes are documented here: https://github.com/microsoft/winget-cli/blob/master/doc/windows/package-actionr/winget/returnCodes.md\n #>\n\n param(\n [Parameter(Mandatory, Position=0)]$Programs,\n\n [Parameter(Mandatory, Position=1)]\n [ValidateSet(\"Install\", \"Uninstall\")]\n [String]$Action\n )\n\n Function Invoke-Winget {\n <#\n .SYNOPSIS\n Invokes the winget.exe with the provided arguments and return the exit code\n\n .PARAMETER wingetId\n The Id of the Program that Winget should Install/Uninstall\n\n .PARAMETER scope\n Determines the installation mode. Can be \"user\" or \"machine\" (For more info look at the winget documentation)\n\n .PARAMETER credential\n The PSCredential Object of the user that should be used to run winget\n\n .NOTES\n Invoke Winget uses the public variable $Action defined outside the function to determine if a Program should be installed or removed\n #>\n param (\n [string]$wingetId,\n [string]$scope = \"\",\n [PScredential]$credential = $null\n )\n\n $commonArguments = \"--id $wingetId --silent\"\n $arguments = if ($Action -eq \"Install\") {\n \"install $commonArguments --accept-source-agreements --accept-package-agreements $(if ($scope) {\" --scope $scope\"})\"\n } else {\n \"uninstall $commonArguments\"\n }\n\n $processParams = @{\n FilePath = \"winget\"\n ArgumentList = $arguments\n Wait = $true\n PassThru = $true\n NoNewWindow = $true\n }\n\n if ($credential) {\n $processParams.credential = $credential\n }\n\n return (Start-Process @processParams).ExitCode\n }\n\n Function Invoke-Install {\n <#\n .SYNOPSIS\n Contains the Install Logic and return code handling from winget\n\n .PARAMETER Program\n The Winget ID of the Program that should be installed\n #>\n param (\n [string]$Program\n )\n $status = Invoke-Winget -wingetId $Program\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully.\"\n return $true\n } elseif ($status -eq -1978335189) {\n Write-Host \"$($Program) No applicable update found\"\n return $true\n }\n\n Write-Host \"Attempt installation of $($Program) with User scope\"\n $status = Invoke-Winget -wingetId $Program -scope \"user\"\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully with User scope.\"\n return $true\n } elseif ($status -eq -1978335189) {\n Write-Host \"$($Program) No applicable update found\"\n return $true\n }\n\n $userChoice = [System.Windows.MessageBox]::Show(\"Do you want to attempt $($Program) installation with specific user credentials? Select 'Yes' to proceed or 'No' to skip.\", \"User credential Prompt\", [System.Windows.MessageBoxButton]::YesNo)\n if ($userChoice -eq 'Yes') {\n $getcreds = Get-Credential\n $status = Invoke-Winget -wingetId $Program -credential $getcreds\n if ($status -eq 0) {\n Write-Host \"$($Program) installed successfully with User prompt.\"\n return $true\n }\n } else {\n Write-Host \"Skipping installation with specific user credentials.\"\n }\n\n Write-Host \"Failed to install $($Program).\"\n return $false\n }\n\n Function Invoke-Uninstall {\n <#\n .SYNOPSIS\n Contains the Uninstall Logic and return code handling from winget\n\n .PARAMETER Program\n The Winget ID of the Program that should be uninstalled\n #>\n param (\n [psobject]$Program\n )\n\n try {\n $status = Invoke-Winget -wingetId $Program\n if ($status -eq 0) {\n Write-Host \"$($Program) uninstalled successfully.\"\n return $true\n } else {\n Write-Host \"Failed to uninstall $($Program).\"\n return $false\n }\n } catch {\n Write-Host \"Failed to uninstall $($Program) due to an error: $_\"\n return $false\n }\n }\n\n $count = $Programs.Count\n $failedPackages = @()\n\n Write-Host \"===========================================\"\n Write-Host \"-- Configuring winget packages ---\"\n Write-Host \"===========================================\"\n\n for ($i = 0; $i -lt $count; $i++) {\n $Program = $Programs[$i]\n $result = $false\n Set-WinUtilProgressBar -label \"$Action $($Program)\" -percent ($i / $count * 100)\n $sync.form.Dispatcher.Invoke([action]{ Set-WinUtilTaskbaritem -value ($i / $count)})\n\n $result = switch ($Action) {\n \"Install\" {Invoke-Install -Program $Program}\n \"Uninstall\" {Invoke-Uninstall -Program $Program}\n default {throw \"[Install-WinUtilProgramWinget] Invalid action: $Action\"}\n }\n\n if (-not $result) {\n $failedPackages += $Program\n }\n }\n\n Set-WinUtilProgressBar -label \"$($Action)ation done\" -percent 100\n return $failedPackages\n}\n
function Set-WinUtilProgressbar{\n <#\n .SYNOPSIS\n This function is used to Update the Progress Bar displayed in the winutil GUI.\n It will be automatically hidden if the user clicks something and no process is running\n .PARAMETER Label\n The Text to be overlayed onto the Progress Bar\n .PARAMETER PERCENT\n The percentage of the Progress Bar that should be filled (0-100)\n .PARAMETER Hide\n If provided, the Progress Bar and the label will be hidden\n #>\n param(\n [string]$Label,\n [ValidateRange(0,100)]\n [int]$Percent,\n $Hide\n )\n if ($hide) {\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Visibility = \"Collapsed\"})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBar.Visibility = \"Collapsed\"})\n } else {\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Visibility = \"Visible\"})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBar.Visibility = \"Visible\"})\n }\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Content.Text = $label})\n $sync.form.Dispatcher.Invoke([action]{$sync.ProgressBarLabel.Content.ToolTip = $label})\n $sync.form.Dispatcher.Invoke([action]{ $sync.ProgressBar.Value = $percent})\n\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
This will create an Environment Variable called 'POWERSHELL_TELEMETRY_OPTOUT' with a value of '1' which will tell Powershell 7 to not send Telemetry Data.
Preview Code
{\n \"Content\": \"Disable Powershell 7 Telemetry\",\n \"Description\": \"This will create an Environment Variable called 'POWERSHELL_TELEMETRY_OPTOUT' with a value of '1' which will tell Powershell 7 to not send Telemetry Data.\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Order\": \"a009_\",\n \"InvokeScript\": [\n \"[Environment]::SetEnvironmentVariable('POWERSHELL_TELEMETRY_OPTOUT', '1', 'Machine')\"\n ],\n \"UndoScript\": [\n \"[Environment]::SetEnvironmentVariable('POWERSHELL_TELEMETRY_OPTOUT', '', 'Machine')\"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/Powershell7Tele\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Creates a restore point at runtime in case a revert is needed from WinUtil modifications
Preview Code
{\n \"Content\": \"Create Restore Point\",\n \"Description\": \"Creates a restore point at runtime in case a revert is needed from WinUtil modifications\",\n \"category\": \"Essential Tweaks\",\n \"panel\": \"1\",\n \"Checked\": \"False\",\n \"Order\": \"a001_\",\n \"InvokeScript\": [\n \"\n # Check if the user has administrative privileges\n if (-Not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {\n Write-Host \\\"Please run this script as an administrator.\\\"\n return\n }\n\n # Check if System Restore is enabled for the main drive\n try {\n # Try getting restore points to check if System Restore is enabled\n Enable-ComputerRestore -Drive \\\"$env:SystemDrive\\\"\n } catch {\n Write-Host \\\"An error occurred while enabling System Restore: $_\\\"\n }\n\n # Check if the SystemRestorePointCreationFrequency value exists\n $exists = Get-ItemProperty -path \\\"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows NT\\\\CurrentVersion\\\\SystemRestore\\\" -Name \\\"SystemRestorePointCreationFrequency\\\" -ErrorAction SilentlyContinue\n if($null -eq $exists) {\n write-host 'Changing system to allow multiple restore points per day'\n Set-ItemProperty -Path \\\"HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows NT\\\\CurrentVersion\\\\SystemRestore\\\" -Name \\\"SystemRestorePointCreationFrequency\\\" -Value \\\"0\\\" -Type DWord -Force -ErrorAction Stop | Out-Null\n }\n\n # Attempt to load the required module for Get-ComputerRestorePoint\n try {\n Import-Module Microsoft.PowerShell.Management -ErrorAction Stop\n } catch {\n Write-Host \\\"Failed to load the Microsoft.PowerShell.Management module: $_\\\"\n return\n }\n\n # Get all the restore points for the current day\n try {\n $existingRestorePoints = Get-ComputerRestorePoint | Where-Object { $_.CreationTime.Date -eq (Get-Date).Date }\n } catch {\n Write-Host \\\"Failed to retrieve restore points: $_\\\"\n return\n }\n\n # Check if there is already a restore point created today\n if ($existingRestorePoints.Count -eq 0) {\n $description = \\\"System Restore Point created by WinUtil\\\"\n\n Checkpoint-Computer -Description $description -RestorePointType \\\"MODIFY_SETTINGS\\\"\n Write-Host -ForegroundColor Green \\\"System Restore Point Created Successfully\\\"\n }\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/Essential-Tweaks/RestorePoint\"\n}\n
# Check if the user has administrative privileges\n if (-Not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {\n Write-Host \"Please run this script as an administrator.\"\n return\n }\n\n # Check if System Restore is enabled for the main drive\n try {\n # Try getting restore points to check if System Restore is enabled\n Enable-ComputerRestore -Drive \"$env:SystemDrive\"\n } catch {\n Write-Host \"An error occurred while enabling System Restore: $_\"\n }\n\n # Check if the SystemRestorePointCreationFrequency value exists\n $exists = Get-ItemProperty -path \"HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SystemRestore\" -Name \"SystemRestorePointCreationFrequency\" -ErrorAction SilentlyContinue\n if($null -eq $exists) {\n write-host 'Changing system to allow multiple restore points per day'\n Set-ItemProperty -Path \"HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\SystemRestore\" -Name \"SystemRestorePointCreationFrequency\" -Value \"0\" -Type DWord -Force -ErrorAction Stop | Out-Null\n }\n\n # Attempt to load the required module for Get-ComputerRestorePoint\n try {\n Import-Module Microsoft.PowerShell.Management -ErrorAction Stop\n } catch {\n Write-Host \"Failed to load the Microsoft.PowerShell.Management module: $_\"\n return\n }\n\n # Get all the restore points for the current day\n try {\n $existingRestorePoints = Get-ComputerRestorePoint | Where-Object { $_.CreationTime.Date -eq (Get-Date).Date }\n } catch {\n Write-Host \"Failed to retrieve restore points: $_\"\n return\n }\n\n # Check if there is already a restore point created today\n if ($existingRestorePoints.Count -eq 0) {\n $description = \"System Restore Point created by WinUtil\"\n\n Checkpoint-Computer -Description $description -RestorePointType \"MODIFY_SETTINGS\"\n Write-Host -ForegroundColor Green \"System Restore Point Created Successfully\"\n }\n
View the JSON file
"},{"location":"dev/tweaks/Essential-Tweaks/Services/","title":"Set Services to Manual","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Turns a bunch of system services to manual that don't need to be running all the time. This is pretty harmless as if the service is needed, it will simply start on demand.
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
Windows scheduled tasks are used to run scripts or programs at specific times or events. Disabling unnecessary tasks can improve system performance and reduce unwanted background activity.
You can find information about scheduled tasks on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/Performance-Plans/AddUltPerf/","title":"Add and Activate Ultimate Performance Profile","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Invoke-WPFUltimatePerformance {\n <#\n\n .SYNOPSIS\n Creates or removes the Ultimate Performance power scheme\n\n .PARAMETER State\n Indicates whether to enable or disable the Ultimate Performance power scheme\n\n #>\n param($State)\n try {\n # Check if Ultimate Performance plan is installed\n $ultimatePlan = powercfg -list | Select-String -Pattern \"Ultimate Performance\"\n if($state -eq \"Enable\") {\n if ($ultimatePlan) {\n Write-Host \"Ultimate Performance plan is already installed.\"\n } else {\n Write-Host \"Installing Ultimate Performance plan...\"\n powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61\n Write-Host \"> Ultimate Performance plan installed.\"\n }\n\n # Set the Ultimate Performance plan as active\n $ultimatePlanGUID = (powercfg -list | Select-String -Pattern \"Ultimate Performance\").Line.Split()[3]\n powercfg -setactive $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan is now active.\"\n\n\n }\n elseif($state -eq \"Disable\") {\n if ($ultimatePlan) {\n # Extract the GUID of the Ultimate Performance plan\n $ultimatePlanGUID = $ultimatePlan.Line.Split()[3]\n\n # Set a different power plan as active before deleting the Ultimate Performance plan\n $balancedPlanGUID = (powercfg -list | Select-String -Pattern \"Balanced\").Line.Split()[3]\n powercfg -setactive $balancedPlanGUID\n\n # Delete the Ultimate Performance plan\n powercfg -delete $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan has been uninstalled.\"\n Write-Host \"> Balanced plan is now active.\"\n } else {\n Write-Host \"Ultimate Performance plan is not installed.\"\n }\n }\n } catch {\n Write-Warning $psitem.Exception.Message\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Invoke-WPFUltimatePerformance {\n <#\n\n .SYNOPSIS\n Creates or removes the Ultimate Performance power scheme\n\n .PARAMETER State\n Indicates whether to enable or disable the Ultimate Performance power scheme\n\n #>\n param($State)\n try {\n # Check if Ultimate Performance plan is installed\n $ultimatePlan = powercfg -list | Select-String -Pattern \"Ultimate Performance\"\n if($state -eq \"Enable\") {\n if ($ultimatePlan) {\n Write-Host \"Ultimate Performance plan is already installed.\"\n } else {\n Write-Host \"Installing Ultimate Performance plan...\"\n powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61\n Write-Host \"> Ultimate Performance plan installed.\"\n }\n\n # Set the Ultimate Performance plan as active\n $ultimatePlanGUID = (powercfg -list | Select-String -Pattern \"Ultimate Performance\").Line.Split()[3]\n powercfg -setactive $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan is now active.\"\n\n\n }\n elseif($state -eq \"Disable\") {\n if ($ultimatePlan) {\n # Extract the GUID of the Ultimate Performance plan\n $ultimatePlanGUID = $ultimatePlan.Line.Split()[3]\n\n # Set a different power plan as active before deleting the Ultimate Performance plan\n $balancedPlanGUID = (powercfg -list | Select-String -Pattern \"Balanced\").Line.Split()[3]\n powercfg -setactive $balancedPlanGUID\n\n # Delete the Ultimate Performance plan\n powercfg -delete $ultimatePlanGUID\n\n Write-Host \"Ultimate Performance plan has been uninstalled.\"\n Write-Host \"> Balanced plan is now active.\"\n } else {\n Write-Host \"Ultimate Performance plan is not installed.\"\n }\n }\n } catch {\n Write-Warning $psitem.Exception.Message\n }\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFShortcut {\n <#\n\n .SYNOPSIS\n Creates a shortcut and prompts for a save location\n\n .PARAMETER ShortcutToAdd\n The name of the shortcut to add\n\n .PARAMETER RunAsAdmin\n A boolean value to make 'Run as administrator' property on (true) or off (false), defaults to off\n\n #>\n param(\n $ShortcutToAdd,\n [bool]$RunAsAdmin = $false\n )\n\n # Preper the Shortcut Fields and add an a Custom Icon if it's available, else don't add a Custom Icon.\n\n Switch ($ShortcutToAdd) {\n \"WinUtil\" {\n # Use Powershell 7 if installed and fallback to PS5 if not\n if (Get-Command \"pwsh\" -ErrorAction SilentlyContinue) {\n $shell = \"pwsh.exe\"\n } else {\n $shell = \"powershell.exe\"\n }\n\n $shellArgs = \"-ExecutionPolicy Bypass -Command `\"Start-Process $shell -verb runas -ArgumentList `'-Command `\"irm https://github.com/ChrisTitusTech/winutil/releases/latest/download/winutil.ps1 | iex`\"`'\"\n\n $DestinationName = \"WinUtil.lnk\"\n }\n }\n\n # Show a File Dialog Browser, to let the User choose the Name and Location of where to save the Shortcut\n $FileBrowser = New-Object System.Windows.Forms.SaveFileDialog\n $FileBrowser.InitialDirectory = [Environment]::GetFolderPath('Desktop')\n $FileBrowser.Filter = \"Shortcut Files (*.lnk)|*.lnk\"\n $FileBrowser.FileName = $DestinationName\n\n # Do an Early Return if the Save Operation was canceled by User's Input.\n $FileBrowserResult = $FileBrowser.ShowDialog()\n $DialogResultEnum = New-Object System.Windows.Forms.DialogResult\n if (-not ($FileBrowserResult -eq $DialogResultEnum::OK)) {\n return\n }\n\n # Prepare the Shortcut paramter\n $WshShell = New-Object -comObject WScript.Shell\n $Shortcut = $WshShell.CreateShortcut($FileBrowser.FileName)\n $Shortcut.TargetPath = $shell\n $Shortcut.Arguments = $shellArgs\n if (Test-Path -Path $winutildir[\"logo.ico\"]) {\n $shortcut.IconLocation = $winutildir[\"logo.ico\"]\n }\n\n # Save the Shortcut to disk\n $Shortcut.Save()\n\n if ($RunAsAdmin -eq $true) {\n $bytes = [System.IO.File]::ReadAllBytes($FileBrowser.FileName)\n # Set byte value at position 0x15 in hex, or 21 in decimal, from the value 0x00 to 0x20 in hex\n $bytes[0x15] = $bytes[0x15] -bor 0x20\n [System.IO.File]::WriteAllBytes($FileBrowser.FileName, $bytes)\n }\n\n Write-Host \"Shortcut for $ShortcutToAdd has been saved to $($FileBrowser.FileName) with 'Run as administrator' set to $RunAsAdmin\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
# Define the local path of the HOSTS file\n $localHostsPath = \"C:\\Windows\\System32\\drivers\\etc\\hosts\"\n\n # Load the content of the HOSTS file\n try {\n $hostsContent = Get-Content $localHostsPath -ErrorAction Stop\n } catch {\n Write-Error \"Failed to load the HOSTS file. Error: $_\"\n return\n }\n\n # Initialize flags and buffer for new content\n $recording = $true\n $newContent = @()\n\n # Iterate over each line of the HOSTS file\n foreach ($line in $hostsContent) {\n if ($line -match \"#AdobeNetBlock-start\") {\n $recording = $false\n }\n if ($recording) {\n $newContent += $line\n }\n if ($line -match \"#AdobeNetBlock-end\") {\n $recording = $true\n }\n }\n\n # Write the filtered content back to the HOSTS file\n try {\n $newContent | Set-Content $localHostsPath -Encoding ASCII\n Write-Output \"Successfully removed the AdobeNetBlock section from the HOSTS file.\"\n } catch {\n Write-Error \"Failed to write back to the HOSTS file. Error: $_\"\n }\n\n # Flush the DNS resolver cache\n try {\n Invoke-Expression \"ipconfig /flushdns\"\n Write-Output \"DNS cache flushed successfully.\"\n } catch {\n Write-Error \"Failed to flush DNS cache. Error: $_\"\n }\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/DeBloat/","title":"Remove ALL MS Store Apps - NOT RECOMMENDED","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
USE WITH CAUTION!!!!! This will remove ALL Microsoft store apps other than the essentials to make winget work. Games installed by MS Store ARE INCLUDED!
Preview Code
{\n \"Content\": \"Remove ALL MS Store Apps - NOT RECOMMENDED\",\n \"Description\": \"USE WITH CAUTION!!!!! This will remove ALL Microsoft store apps other than the essentials to make winget work. Games installed by MS Store ARE INCLUDED!\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a028_\",\n \"appx\": [\n \"Microsoft.Microsoft3DViewer\",\n \"Microsoft.AppConnector\",\n \"Microsoft.BingFinance\",\n \"Microsoft.BingNews\",\n \"Microsoft.BingSports\",\n \"Microsoft.BingTranslator\",\n \"Microsoft.BingWeather\",\n \"Microsoft.BingFoodAndDrink\",\n \"Microsoft.BingHealthAndFitness\",\n \"Microsoft.BingTravel\",\n \"Microsoft.MinecraftUWP\",\n \"Microsoft.GamingServices\",\n \"Microsoft.GetHelp\",\n \"Microsoft.Getstarted\",\n \"Microsoft.Messaging\",\n \"Microsoft.Microsoft3DViewer\",\n \"Microsoft.MicrosoftSolitaireCollection\",\n \"Microsoft.NetworkSpeedTest\",\n \"Microsoft.News\",\n \"Microsoft.Office.Lens\",\n \"Microsoft.Office.Sway\",\n \"Microsoft.Office.OneNote\",\n \"Microsoft.OneConnect\",\n \"Microsoft.People\",\n \"Microsoft.Print3D\",\n \"Microsoft.SkypeApp\",\n \"Microsoft.Wallet\",\n \"Microsoft.Whiteboard\",\n \"Microsoft.WindowsAlarms\",\n \"microsoft.windowscommunicationsapps\",\n \"Microsoft.WindowsFeedbackHub\",\n \"Microsoft.WindowsMaps\",\n \"Microsoft.YourPhone\",\n \"Microsoft.WindowsSoundRecorder\",\n \"Microsoft.XboxApp\",\n \"Microsoft.ConnectivityStore\",\n \"Microsoft.ScreenSketch\",\n \"Microsoft.Xbox.TCUI\",\n \"Microsoft.XboxGameOverlay\",\n \"Microsoft.XboxGameCallableUI\",\n \"Microsoft.XboxSpeechToTextOverlay\",\n \"Microsoft.MixedReality.Portal\",\n \"Microsoft.XboxIdentityProvider\",\n \"Microsoft.ZuneMusic\",\n \"Microsoft.ZuneVideo\",\n \"Microsoft.Getstarted\",\n \"Microsoft.MicrosoftOfficeHub\",\n \"*EclipseManager*\",\n \"*ActiproSoftwareLLC*\",\n \"*AdobeSystemsIncorporated.AdobePhotoshopExpress*\",\n \"*Duolingo-LearnLanguagesforFree*\",\n \"*PandoraMediaInc*\",\n \"*CandyCrush*\",\n \"*BubbleWitch3Saga*\",\n \"*Wunderlist*\",\n \"*Flipboard*\",\n \"*Twitter*\",\n \"*Facebook*\",\n \"*Royal Revolt*\",\n \"*Sway*\",\n \"*Speed Test*\",\n \"*Dolby*\",\n \"*Viber*\",\n \"*ACGMediaPlayer*\",\n \"*Netflix*\",\n \"*OneCalendar*\",\n \"*LinkedInforWindows*\",\n \"*HiddenCityMysteryofShadows*\",\n \"*Hulu*\",\n \"*HiddenCity*\",\n \"*AdobePhotoshopExpress*\",\n \"*HotspotShieldFreeVPN*\",\n \"*Microsoft.Advertising.Xaml*\"\n ],\n \"InvokeScript\": [\n \"\n $TeamsPath = [System.IO.Path]::Combine($env:LOCALAPPDATA, 'Microsoft', 'Teams')\n $TeamsUpdateExePath = [System.IO.Path]::Combine($TeamsPath, 'Update.exe')\n\n Write-Host \\\"Stopping Teams process...\\\"\n Stop-Process -Name \\\"*teams*\\\" -Force -ErrorAction SilentlyContinue\n\n Write-Host \\\"Uninstalling Teams from AppData\\\\Microsoft\\\\Teams\\\"\n if ([System.IO.File]::Exists($TeamsUpdateExePath)) {\n # Uninstall app\n $proc = Start-Process $TeamsUpdateExePath \\\"-uninstall -s\\\" -PassThru\n $proc.WaitForExit()\n }\n\n Write-Host \\\"Removing Teams AppxPackage...\\\"\n Get-AppxPackage \\\"*Teams*\\\" | Remove-AppxPackage -ErrorAction SilentlyContinue\n Get-AppxPackage \\\"*Teams*\\\" -AllUsers | Remove-AppxPackage -AllUsers -ErrorAction SilentlyContinue\n\n Write-Host \\\"Deleting Teams directory\\\"\n if ([System.IO.Directory]::Exists($TeamsPath)) {\n Remove-Item $TeamsPath -Force -Recurse -ErrorAction SilentlyContinue\n }\n\n Write-Host \\\"Deleting Teams uninstall registry key\\\"\n # Uninstall from Uninstall registry key UninstallString\n $us = (Get-ChildItem -Path HKLM:\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Uninstall, HKLM:\\\\SOFTWARE\\\\Wow6432Node\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\Uninstall | Get-ItemProperty | Where-Object { $_.DisplayName -like '*Teams*'}).UninstallString\n if ($us.Length -gt 0) {\n $us = ($us.Replace('/I', '/uninstall ') + ' /quiet').Replace(' ', ' ')\n $FilePath = ($us.Substring(0, $us.IndexOf('.exe') + 4).Trim())\n $ProcessArgs = ($us.Substring($us.IndexOf('.exe') + 5).Trim().replace(' ', ' '))\n $proc = Start-Process -FilePath $FilePath -Args $ProcessArgs -PassThru\n $proc.WaitForExit()\n }\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DeBloat\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function CCStopper {\n $path = \"C:\\Program Files (x86)\\Common Files\\Adobe\\Adobe Desktop Common\\ADS\\Adobe Desktop Service.exe\"\n\n # Test if the path exists before proceeding\n if (Test-Path $path) {\n Takeown /f $path\n $acl = Get-Acl $path\n $acl.SetOwner([System.Security.Principal.NTAccount]\"Administrators\")\n $acl | Set-Acl $path\n\n Rename-Item -Path $path -NewName \"Adobe Desktop Service.exe.old\" -Force\n } else {\n Write-Host \"Adobe Desktop Service is not in the default location.\"\n }\n }\n\n\n function AcrobatUpdates {\n # Editing Acrobat Updates. The last folder before the key is dynamic, therefore using a script.\n # Possible Values for the edited key:\n # 0 = Do not download or install updates automatically\n # 2 = Automatically download updates but let the user choose when to install them\n # 3 = Automatically download and install updates (default value)\n # 4 = Notify the user when an update is available but don't download or install it automatically\n # = It notifies the user using Windows Notifications. It runs on startup without having to have a Service/Acrobat/Reader running, therefore 0 is the next best thing.\n\n $rootPath = \"HKLM:\\SOFTWARE\\WOW6432Node\\Adobe\\Adobe ARM\\Legacy\\Acrobat\"\n\n # Get all subkeys under the specified root path\n $subKeys = Get-ChildItem -Path $rootPath | Where-Object { $_.PSChildName -like \"{*}\" }\n\n # Loop through each subkey\n foreach ($subKey in $subKeys) {\n # Get the full registry path\n $fullPath = Join-Path -Path $rootPath -ChildPath $subKey.PSChildName\n try {\n Set-ItemProperty -Path $fullPath -Name Mode -Value 0\n Write-Host \"Acrobat Updates have been disabled.\"\n } catch {\n Write-Host \"Registry Key for changing Acrobat Updates does not exist in $fullPath\"\n }\n }\n }\n\n CCStopper\n AcrobatUpdates\n
Windows services are background processes for system functions or applications. Setting some to manual optimizes performance by starting them only when needed.
You can find information about services on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Disables all Microsoft Store apps from running in the background, which has to be done individually since Win11
Preview Code
{\n \"Content\": \"Disable Background Apps\",\n \"Description\": \"Disables all Microsoft Store apps from running in the background, which has to be done individually since Win11\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a024_\",\n \"registry\": [\n {\n \"Path\": \"HKCU:\\\\Software\\\\Microsoft\\\\Windows\\\\CurrentVersion\\\\BackgroundAccessApplications\",\n \"Name\": \"GlobalUserDisabled\",\n \"Value\": \"1\",\n \"OriginalValue\": \"0\",\n \"Type\": \"DWord\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableBGapps\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableLMS1/","title":"Disable Intel MM (vPro LMS)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Intel LMS service is always listening on all ports and could be a huge security risk. There is no need to run LMS on home machines and even in the Enterprise there are better solutions.
Preview Code
{\n \"Content\": \"Disable Intel MM (vPro LMS)\",\n \"Description\": \"Intel LMS service is always listening on all ports and could be a huge security risk. There is no need to run LMS on home machines and even in the Enterprise there are better solutions.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a026_\",\n \"InvokeScript\": [\n \"\n Write-Host \\\"Kill LMS\\\"\n $serviceName = \\\"LMS\\\"\n Write-Host \\\"Stopping and disabling service: $serviceName\\\"\n Stop-Service -Name $serviceName -Force -ErrorAction SilentlyContinue;\n Set-Service -Name $serviceName -StartupType Disabled -ErrorAction SilentlyContinue;\n\n Write-Host \\\"Removing service: $serviceName\\\";\n sc.exe delete $serviceName;\n\n Write-Host \\\"Removing LMS driver packages\\\";\n $lmsDriverPackages = Get-ChildItem -Path \\\"C:\\\\Windows\\\\System32\\\\DriverStore\\\\FileRepository\\\" -Recurse -Filter \\\"lms.inf*\\\";\n foreach ($package in $lmsDriverPackages) {\n Write-Host \\\"Removing driver package: $($package.Name)\\\";\n pnputil /delete-driver $($package.Name) /uninstall /force;\n }\n if ($lmsDriverPackages.Count -eq 0) {\n Write-Host \\\"No LMS driver packages found in the driver store.\\\";\n } else {\n Write-Host \\\"All found LMS driver packages have been removed.\\\";\n }\n\n Write-Host \\\"Searching and deleting LMS executable files\\\";\n $programFilesDirs = @(\\\"C:\\\\Program Files\\\", \\\"C:\\\\Program Files (x86)\\\");\n $lmsFiles = @();\n foreach ($dir in $programFilesDirs) {\n $lmsFiles += Get-ChildItem -Path $dir -Recurse -Filter \\\"LMS.exe\\\" -ErrorAction SilentlyContinue;\n }\n foreach ($file in $lmsFiles) {\n Write-Host \\\"Taking ownership of file: $($file.FullName)\\\";\n & icacls $($file.FullName) /grant Administrators:F /T /C /Q;\n & takeown /F $($file.FullName) /A /R /D Y;\n Write-Host \\\"Deleting file: $($file.FullName)\\\";\n Remove-Item $($file.FullName) -Force -ErrorAction SilentlyContinue;\n }\n if ($lmsFiles.Count -eq 0) {\n Write-Host \\\"No LMS.exe files found in Program Files directories.\\\";\n } else {\n Write-Host \\\"All found LMS.exe files have been deleted.\\\";\n }\n Write-Host 'Intel LMS vPro service has been disabled, removed, and blocked.';\n \"\n ],\n \"UndoScript\": [\n \"\n Write-Host \\\"LMS vPro needs to be redownloaded from intel.com\\\"\n\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/DisableLMS1\"\n}\n
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/Display/","title":"Set Display for Performance","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
function Invoke-WPFOOSU {\n <#\n .SYNOPSIS\n Downloads and runs OO Shutup 10\n #>\n try {\n $OOSU_filepath = \"$ENV:temp\\OOSU10.exe\"\n $Initial_ProgressPreference = $ProgressPreference\n $ProgressPreference = \"SilentlyContinue\" # Disables the Progress Bar to drasticly speed up Invoke-WebRequest\n Invoke-WebRequest -Uri \"https://dl5.oo-software.com/files/ooshutup10/OOSU10.exe\" -OutFile $OOSU_filepath\n Write-Host \"Starting OO Shutup 10 ...\"\n Start-Process $OOSU_filepath\n } catch {\n Write-Host \"Error Downloading and Running OO Shutup 10\" -ForegroundColor Red\n }\n finally {\n $ProgressPreference = $Initial_ProgressPreference\n }\n}\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveCopilot/","title":"Disable Microsoft Copilot","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveEdge/","title":"Remove Microsoft Edge","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Function Uninstall-WinUtilEdgeBrowser {\n\n <#\n\n .SYNOPSIS\n This will uninstall edge by changing the region to Ireland and uninstalling edge the changing it back\n\n #>\n\n$msedgeProcess = Get-Process -Name \"msedge\" -ErrorAction SilentlyContinue\n$widgetsProcess = Get-Process -Name \"widgets\" -ErrorAction SilentlyContinue\n# Checking if Microsoft Edge is running\nif ($msedgeProcess) {\n Stop-Process -Name \"msedge\" -Force\n} else {\n Write-Output \"msedge process is not running.\"\n}\n# Checking if Widgets is running\nif ($widgetsProcess) {\n Stop-Process -Name \"widgets\" -Force\n} else {\n Write-Output \"widgets process is not running.\"\n}\n\nfunction Uninstall-Process {\n param (\n [Parameter(Mandatory = $true)]\n [string]$Key\n )\n\n $originalNation = [microsoft.win32.registry]::GetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', [Microsoft.Win32.RegistryValueKind]::String)\n\n # Set Nation to 84 (France) temporarily\n [microsoft.win32.registry]::SetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', 68, [Microsoft.Win32.RegistryValueKind]::String) | Out-Null\n\n # credits to he3als for the Acl commands\n $fileName = \"IntegratedServicesRegionPolicySet.json\"\n $pathISRPS = [Environment]::SystemDirectory + \"\\\" + $fileName\n $aclISRPS = Get-Acl -Path $pathISRPS\n $aclISRPSBackup = [System.Security.AccessControl.FileSecurity]::new()\n $aclISRPSBackup.SetSecurityDescriptorSddlForm($acl.Sddl)\n if (Test-Path -Path $pathISRPS) {\n try {\n $admin = [System.Security.Principal.NTAccount]$(New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-544')).Translate([System.Security.Principal.NTAccount]).Value\n\n $aclISRPS.SetOwner($admin)\n $rule = New-Object System.Security.AccessControl.FileSystemAccessRule($admin, 'FullControl', 'Allow')\n $aclISRPS.AddAccessRule($rule)\n Set-Acl -Path $pathISRPS -AclObject $aclISRPS\n\n Rename-Item -Path $pathISRPS -NewName ($fileName + '.bak') -Force\n }\n catch {\n Write-Error \"[$Mode] Failed to set owner for $pathISRPS\"\n }\n }\n\n $baseKey = 'HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdate'\n $registryPath = $baseKey + '\\ClientState\\' + $Key\n\n if (!(Test-Path -Path $registryPath)) {\n Write-Host \"[$Mode] Registry key not found: $registryPath\"\n return\n }\n\n Remove-ItemProperty -Path $registryPath -Name \"experiment_control_labels\" -ErrorAction SilentlyContinue | Out-Null\n\n $uninstallString = (Get-ItemProperty -Path $registryPath).UninstallString\n $uninstallArguments = (Get-ItemProperty -Path $registryPath).UninstallArguments\n\n if ([string]::IsNullOrEmpty($uninstallString) -or [string]::IsNullOrEmpty($uninstallArguments)) {\n Write-Host \"[$Mode] Cannot find uninstall methods for $Mode\"\n return\n }\n\n $uninstallArguments += \" --force-uninstall --delete-profile\"\n\n # $uninstallCommand = \"`\"$uninstallString`\"\" + $uninstallArguments\n if (!(Test-Path -Path $uninstallString)) {\n Write-Host \"[$Mode] setup.exe not found at: $uninstallString\"\n return\n }\n Start-Process -FilePath $uninstallString -ArgumentList $uninstallArguments -Wait -NoNewWindow -Verbose\n\n # Restore Acl\n if (Test-Path -Path ($pathISRPS + '.bak')) {\n Rename-Item -Path ($pathISRPS + '.bak') -NewName $fileName -Force\n Set-Acl -Path $pathISRPS -AclObject $aclISRPSBackup\n }\n\n # Restore Nation\n [microsoft.win32.registry]::SetValue('HKEY_USERS\\.DEFAULT\\Control Panel\\International\\Geo', 'Nation', $originalNation, [Microsoft.Win32.RegistryValueKind]::String) | Out-Null\n\n if ((Get-ItemProperty -Path $baseKey).IsEdgeStableUninstalled -eq 1) {\n Write-Host \"[$Mode] Edge Stable has been successfully uninstalled\"\n }\n}\n\nfunction Uninstall-Edge {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft Edge\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n [microsoft.win32.registry]::SetValue(\"HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdateDev\", \"AllowUninstall\", 1, [Microsoft.Win32.RegistryValueKind]::DWord) | Out-Null\n\n Uninstall-Process -Key '{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}'\n\n @( \"$env:ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\",\n \"$env:PUBLIC\\Desktop\",\n \"$env:USERPROFILE\\Desktop\" ) | ForEach-Object {\n $shortcutPath = Join-Path -Path $_ -ChildPath \"Microsoft Edge.lnk\"\n if (Test-Path -Path $shortcutPath) {\n Remove-Item -Path $shortcutPath -Force\n }\n }\n\n}\n\nfunction Uninstall-WebView {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft EdgeWebView\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n # Force to use system-wide WebView2\n # [microsoft.win32.registry]::SetValue(\"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Edge\\WebView2\\BrowserExecutableFolder\", \"*\", \"%%SystemRoot%%\\System32\\Microsoft-Edge-WebView\")\n\n Uninstall-Process -Key '{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}'\n}\n\nfunction Uninstall-EdgeUpdate {\n Remove-ItemProperty -Path \"HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Microsoft Edge Update\" -Name \"NoRemove\" -ErrorAction SilentlyContinue | Out-Null\n\n $registryPath = 'HKLM:\\SOFTWARE\\WOW6432Node\\Microsoft\\EdgeUpdate'\n if (!(Test-Path -Path $registryPath)) {\n Write-Host \"Registry key not found: $registryPath\"\n return\n }\n $uninstallCmdLine = (Get-ItemProperty -Path $registryPath).UninstallCmdLine\n\n if ([string]::IsNullOrEmpty($uninstallCmdLine)) {\n Write-Host \"Cannot find uninstall methods for $Mode\"\n return\n }\n\n Write-Output \"Uninstalling: $uninstallCmdLine\"\n Start-Process cmd.exe \"/c $uninstallCmdLine\" -WindowStyle Hidden -Wait\n}\n\nUninstall-Edge\n # \"WebView\" { Uninstall-WebView }\n # \"EdgeUpdate\" { Uninstall-EdgeUpdate }\n\n\n\n\n}\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/RemoveHomeGallery/","title":"Remove Home and Gallery from explorer","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Great Windows 11 tweak to bring back good context menus when right clicking things in explorer.
Preview Code
{\n \"Content\": \"Set Classic Right-Click Menu \",\n \"Description\": \"Great Windows 11 tweak to bring back good context menus when right clicking things in explorer.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a027_\",\n \"InvokeScript\": [\n \"\n New-Item -Path \\\"HKCU:\\\\Software\\\\Classes\\\\CLSID\\\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\\\" -Name \\\"InprocServer32\\\" -force -value \\\"\\\"\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \\\"explorer\\\"\n Stop-Process -InputObject $process\n \"\n ],\n \"UndoScript\": [\n \"\n Remove-Item -Path \\\"HKCU:\\\\Software\\\\Classes\\\\CLSID\\\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\\\" -Recurse -Confirm:$false -Force\n # Restarting Explorer in the Undo Script might not be necessary, as the Registry change without restarting Explorer does work, but just to make sure.\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \\\"explorer\\\"\n Stop-Process -InputObject $process\n \"\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/RightClickMenu\"\n}\n
Remove-Item -Path \"HKCU:\\Software\\Classes\\CLSID\\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\" -Recurse -Confirm:$false -Force\n # Restarting Explorer in the Undo Script might not be necessary, as the Registry change without restarting Explorer does work, but just to make sure.\n Write-Host Restarting explorer.exe ...\n $process = Get-Process -Name \"explorer\"\n Stop-Process -InputObject $process\n
View the JSON file
"},{"location":"dev/tweaks/z--Advanced-Tweaks---CAUTION/UTC/","title":"Set Time to UTC (Dual Boot)","text":"
Last Updated: 2024-08-07
Info
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Essential for computers that are dual booting. Fixes the time sync with Linux Systems.
Preview Code
{\n \"Content\": \"Set Time to UTC (Dual Boot)\",\n \"Description\": \"Essential for computers that are dual booting. Fixes the time sync with Linux Systems.\",\n \"category\": \"z__Advanced Tweaks - CAUTION\",\n \"panel\": \"1\",\n \"Order\": \"a027_\",\n \"registry\": [\n {\n \"Path\": \"HKLM:\\\\SYSTEM\\\\CurrentControlSet\\\\Control\\\\TimeZoneInformation\",\n \"Name\": \"RealTimeIsUniversal\",\n \"Type\": \"DWord\",\n \"Value\": \"1\",\n \"OriginalValue\": \"0\"\n }\n ],\n \"link\": \"https://christitustech.github.io/winutil/dev/tweaks/z--Advanced-Tweaks---CAUTION/UTC\"\n}\n
Applications and System Components store and retrieve configuration data to modify windows settings, so we can use the registry to change many settings in one place.
You can find information about the registry on Wikipedia and Microsoft's Website.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
The Development Documentation is auto generated for every compilation of WinUtil, meaning a part of it will always stay up-to-date. Developers do have the ability to add custom content, which won't be updated automatically.
Essential Tweaks are modifications and optimizations that are generally safe for most users to implement. These tweaks are designed to enhance system performance, improve privacy, and reduce unnecessary system activities. They are considered low-risk and are recommended for users who want to ensure their system runs smoothly and efficiently without delving too deeply into complex configurations. The goal of Essential Tweaks is to provide noticeable improvements with minimal risk, making them suitable for a wide range of users, including those who may not have advanced technical knowledge.
Advanced Tweaks are intended for experienced users who have a solid understanding of their system and the potential implications of making deep-level changes. These tweaks involve more significant alterations to the operating system and can provide substantial customization. However, they also carry a higher risk of causing system instability or unintended side effects if not implemented correctly. Users who choose to apply Advanced Tweaks should proceed with caution, ensuring they have adequate knowledge and backups in place to recover if something goes wrong. These tweaks are not recommended for novice users or those unfamiliar with the inner workings of their operating system.
O&O ShutUp10++ can be launched from WinUtil with only one button click. It is a free privacy tool for Windows that lets users easily manage their privacy settings. It disables telemetry, controls updates, and manages app permissions to enhance security and privacy. The tool offers recommended settings for optimal privacy with just a few clicks.
The utility provides a convenient DNS selection feature, allowing users to choose between various DNS providers for both IPv4 and IPv6. This enables users to optimize their internet connection for speed, security, and privacy according to their specific needs. Here are the available options:
Default: Uses the default DNS settings configured by your ISP or network.
DHCP: Automatically acquires DNS settings from the DHCP server.
Google: A reliable and fast DNS service provided by Google.
Cloudflare: Known for speed and privacy, Cloudflare DNS is a popular choice for enhancing internet performance.
Cloudflare_Malware: Provides additional protection by blocking malware sites.
Cloudflare_Malware_Adult: Blocks both malware and adult content, offering more comprehensive filtering.
Level3: Another fast and reliable DNS service option.
Open_DNS: Offers customizable filtering and enhanced security features.
Quad9: Focuses on security by blocking known malicious domains.
The Customize Preferences section allows users to personalize their Windows experience by toggling various visual and functional features. These preferences are designed to enhance usability and tailor the system to the user’s specific needs and preferences.
The Performance Plans section allows users to manage the Ultimate Performance Profile on their system. This feature is designed to optimize the system for maximum performance.
Add and activate the Ultimate Performance Profile:¶
Enables and activates the Ultimate Performance Profile to enhance system performance by minimizing latency and increasing efficiency.
The utility provides three distinct settings for managing Windows updates: Default (Out of Box) Settings, Security (Recommended) Settings, and Disable ALL Updates (NOT RECOMMENDED!). Each setting offers a different approach to handling updates, catering to various user needs and preferences.
Description: This setting retains the default configurations that come with Windows, ensuring no modifications are made.
Functionality: It will remove any custom Windows update settings previously applied.
Note: If update errors persist, reset all updates in the configuration tab to restore all Microsoft Update Services to their default settings, reinstalling them from their servers.
Description: This is the recommended setting for all computers.
Update Schedule:
Feature Updates: Delays feature updates by 2 years to avoid potential bugs and instability.
Security Updates: Installs security updates 4 days after their release to ensure system protection against pressing security flaws.
Rationale:
Feature Updates: Often introduce new features and bugs; delaying these updates minimizes the risk of system disruptions.
Security Updates: Essential for patching critical security vulnerabilities. Delaying them by a few days allows for verification of stability and compatibility without leaving the system exposed for extended periods.
If you don't have a Windows ISO file prepared, you can download it using the Media Creation Tool for the respective Windows version. Here is the Windows 11 version, and here is the Windows 10 version
Configure the debloat process.
Specify the target location for the new ISO file.
Let the magic happen!
Heads-up
This feature is still in development, and you may encounter some issues with the generated images. If that happens, don't hesitate to report an issue!
Selecting a scratch directory will copy the contents of the ISO file to the directory you specify instead of an automatically generated folder in the %TEMP% directory.
You can select an edition of Windows to debloat (SKU) using the convenient drop-down menu.
By default, MicroWin will debloat the Pro edition, but you can choose any edition you want.
Keep Provisioned Packages: leaving this option unticked (default) will try to remove every operating system package.
Some packages may remain after processing. This can happen if the packages in question are permanent or have been superseded by newer versions.
Keep Appx Packages: leaving this option unticked (default) will try to remove every Microsoft Store app from the Windows image.
This option will exclude some applications that are essential in the event that you want or need to add a Store app later on.
Keep Defender: leaving this option unticked will try to remove every part of Windows Defender, including the Windows Security app.
Leaving this option unticked is NOT recommended unless you plan to use a third-party antivirus solution on your MicroWin installation. In that regard, don't install AVs with bad reputations or rogueware.
Keep Edge: leaving this option unticked will try to remove every part of the Microsoft Edge browser using the best methods available.
Leaving this option unticked is not recommended because it might break some applications that might depend on the Edge WebView2 runtime. However, if that happens, you can easily reinstall it
Inject drivers will add the drivers in the folder that you specify to the target Windows image.
Import drivers from the current system will add every third-party driver that is present in your active installation.
This makes the target image have the same hardware compatibility as the active installation. However, this means that you will only be able to install the target Windows image and take full advantage of it on computers with the same hardware. To avoid this, you'll need to customize the install.wim file of the target ISO in the 'sources` folder.
Copy to Ventoy will copy the target ISO file to any USB drive with Ventoy installed
Info
Ventoy is a solution that lets you boot to any ISO file stored on a drive. Think of it as having multiple bootable USBs in one. Do note, though, that your drive needs to have enough free space for the target ISO file.
Some features are available through automation. This allows you to save your config file, pass it to WinUtil, walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
On the Install Tab, click "Get Installed", this will get all installed apps supported by Winutil on the system.
Click on the Settings cog in the upper right corner and choose Export. Choose file file and location; this will export the setting file.
Copy this file to a USB or somewhere you can use it after Windows installation.
Tip
Use the Microwin tab to create a custom Windows image & install the Windows image.
On any supported Windows machine, open PowerShell as Admin and run the following command to automatically apply tweaks and install apps from the config file.
Essential Tweaks are modifications and optimizations that are generally safe for most users to implement. These tweaks are designed to enhance system performance, improve privacy, and reduce unnecessary system activities. They are considered low-risk and are recommended for users who want to ensure their system runs smoothly and efficiently without delving too deeply into complex configurations. The goal of Essential Tweaks is to provide noticeable improvements with minimal risk, making them suitable for a wide range of users, including those who may not have advanced technical knowledge.
Advanced Tweaks are intended for experienced users who have a solid understanding of their system and the potential implications of making deep-level changes. These tweaks involve more significant alterations to the operating system and can provide substantial customization. However, they also carry a higher risk of causing system instability or unintended side effects if not implemented correctly. Users who choose to apply Advanced Tweaks should proceed with caution, ensuring they have adequate knowledge and backups in place to recover if something goes wrong. These tweaks are not recommended for novice users or those unfamiliar with the inner workings of their operating system.
O&O ShutUp10++ can be launched from WinUtil with only one button click. It is a free privacy tool for Windows that lets users easily manage their privacy settings. It disables telemetry, controls updates, and manages app permissions to enhance security and privacy. The tool offers recommended settings for optimal privacy with just a few clicks.
The utility provides a convenient DNS selection feature, allowing users to choose between various DNS providers for both IPv4 and IPv6. This enables users to optimize their internet connection for speed, security, and privacy according to their specific needs. Here are the available options:
Default: Uses the default DNS settings configured by your ISP or network.
DHCP: Automatically acquires DNS settings from the DHCP server.
Google: A reliable and fast DNS service provided by Google.
Cloudflare: Known for speed and privacy, Cloudflare DNS is a popular choice for enhancing internet performance.
Cloudflare_Malware: Provides additional protection by blocking malware sites.
Cloudflare_Malware_Adult: Blocks both malware and adult content, offering more comprehensive filtering.
Level3: Another fast and reliable DNS service option.
Open_DNS: Offers customizable filtering and enhanced security features.
Quad9: Focuses on security by blocking known malicious domains.
The Customize Preferences section allows users to personalize their Windows experience by toggling various visual and functional features. These preferences are designed to enhance usability and tailor the system to the user’s specific needs and preferences.
The Performance Plans section allows users to manage the Ultimate Performance Profile on their system. This feature is designed to optimize the system for maximum performance.
Add and activate the Ultimate Performance Profile:¶
Enables and activates the Ultimate Performance Profile to enhance system performance by minimizing latency and increasing efficiency.
The utility provides three distinct settings for managing Windows updates: Default (Out of Box) Settings, Security (Recommended) Settings, and Disable ALL Updates (NOT RECOMMENDED!). Each setting offers a different approach to handling updates, catering to various user needs and preferences.
Description: This setting retains the default configurations that come with Windows, ensuring no modifications are made.
Functionality: It will remove any custom Windows update settings previously applied.
Note: If update errors persist, reset all updates in the configuration tab to restore all Microsoft Update Services to their default settings, reinstalling them from their servers.
Description: This is the recommended setting for all computers.
Update Schedule:
Feature Updates: Delays feature updates by 2 years to avoid potential bugs and instability.
Security Updates: Installs security updates 4 days after their release to ensure system protection against pressing security flaws.
Rationale:
Feature Updates: Often introduce new features and bugs; delaying these updates minimizes the risk of system disruptions.
Security Updates: Essential for patching critical security vulnerabilities. Delaying them by a few days allows for verification of stability and compatibility without leaving the system exposed for extended periods.
If you don't have a Windows ISO file prepared, you can download it using the Media Creation Tool for the respective Windows version. Here is the Windows 11 version, and here is the Windows 10 version
Configure the debloat process.
Specify the target location for the new ISO file.
Let the magic happen!
Heads-up
This feature is still in development, and you may encounter some issues with the generated images. If that happens, don't hesitate to report an issue!
Selecting a scratch directory will copy the contents of the ISO file to the directory you specify instead of an automatically generated folder in the %TEMP% directory.
You can select an edition of Windows to debloat (SKU) using the convenient drop-down menu.
By default, MicroWin will debloat the Pro edition, but you can choose any edition you want.
Inject drivers will add the drivers in the folder that you specify to the target Windows image.
Import drivers from the current system will add every third-party driver that is present in your active installation.
This makes the target image have the same hardware compatibility as the active installation. However, this means that you will only be able to install the target Windows image and take full advantage of it on computers with the same hardware. To avoid this, you'll need to customize the install.wim file of the target ISO in the 'sources` folder.
With MicroWin, you can also configure your user before proceeding if you don't want to use the default User account. To do this, simply type the account name (20 characters maximum), and a password. Then, let MicroWin do the rest.
Info
Please make sure that you remember your password. MicroWin will configure auto-login settings, so you won't have to enter your password. However, if you are required to enter your password, it's best that you don't forget it.
Copy to Ventoy will copy the target ISO file to any USB drive with Ventoy installed
Info
Ventoy is a solution that lets you boot to any ISO file stored on a drive. Think of it as having multiple bootable USBs in one. Do note, though, that your drive needs to have enough free space for the target ISO file.
Some features are available through automation. This allows you to save your config file, pass it to WinUtil, walk away and come back to a finished system. Here is how you can set it up currently with Winutil >24.01.15
On the Install Tab, click "Get Installed", this will get all installed apps supported by Winutil on the system.
Click on the Settings cog in the upper right corner and choose Export. Choose file file and location; this will export the setting file.
Copy this file to a USB or somewhere you can use it after Windows installation.
Tip
Use the Microwin tab to create a custom Windows image & install the Windows image.
On any supported Windows machine, open PowerShell as Admin and run the following command to automatically apply tweaks and install apps from the config file.
