Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
404 - Not found
\ No newline at end of file
+ WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
404 - Not found
\ No newline at end of file
diff --git a/CONTRIBUTING/index.html b/CONTRIBUTING/index.html
new file mode 100644
index 00000000..ddf599f1
--- /dev/null
+++ b/CONTRIBUTING/index.html
@@ -0,0 +1,15 @@
+ Contributing Guide - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
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.
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.
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.
\ No newline at end of file
diff --git a/KnownIssues/index.html b/KnownIssues/index.html
index f88802c9..5302e9a7 100644
--- a/KnownIssues/index.html
+++ b/KnownIssues/index.html
@@ -1,4 +1,4 @@
- Known Issues - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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:
[Net.ServicePointManager]::SecurityProtocol=[Net.SecurityProtocolType]::Tls12;iex(New-ObjectNet.WebClient).DownloadString('https://github.com/ChrisTitusTech/winutil/releases/latest/download/winutil.ps1')
+ Known Issues - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
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.
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.
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.
\ No newline at end of file
diff --git a/dev/features/Features/DisableLegacyRecovery/index.html b/dev/features/Features/DisableLegacyRecovery/index.html
index 08cf453c..4bb9b1af 100644
--- a/dev/features/Features/DisableLegacyRecovery/index.html
+++ b/dev/features/Features/DisableLegacyRecovery/index.html
@@ -1,4 +1,4 @@
- Disable Legacy F8 Boot Recovery - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
Disable Search Box Web Suggestions in Registry(explorer restart)¶
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
Disable Search Box Web Suggestions in Registry(explorer restart)¶
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
Enable Search Box Web Suggestions in Registry(explorer restart)¶
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
Enable Search Box Web Suggestions in Registry(explorer restart)¶
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.
Enables web suggestions when searching using Windows Search.
Preview Code
{"Content":"Enable Search Box Web Suggestions in Registry(explorer restart)","Description":"Enables web suggestions when searching using Windows Search.","category":"Features",
diff --git a/dev/features/Features/Install/index.html b/dev/features/Features/Install/index.html
index 2a60cbb6..1c706af9 100644
--- a/dev/features/Features/Install/index.html
+++ b/dev/features/Features/Install/index.html
@@ -1,4 +1,4 @@
- Install Features - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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
{
+ All .Net Framework (2,3,4) - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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
{"Content":"All .Net Framework (2,3,4)","Description":".NET and .NET Framework is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.","category":"Features",
diff --git a/dev/features/Features/hyperv/index.html b/dev/features/Features/hyperv/index.html
index 7ccb2521..945f9b00 100644
--- a/dev/features/Features/hyperv/index.html
+++ b/dev/features/Features/hyperv/index.html
@@ -1,4 +1,4 @@
- HyperV Virtualization - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Hyper-V is a hardware virtualization product developed by Microsoft that allows users to create and manage virtual machines.
Preview Code
{"Content":"HyperV Virtualization","Description":"Hyper-V is a hardware virtualization product developed by Microsoft that allows users to create and manage virtual machines.","category":"Features",
diff --git a/dev/features/Features/legacymedia/index.html b/dev/features/Features/legacymedia/index.html
index b0376845..b5dafb9e 100644
--- a/dev/features/Features/legacymedia/index.html
+++ b/dev/features/Features/legacymedia/index.html
@@ -1,4 +1,4 @@
- Legacy Media (WMP, DirectPlay) - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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.
Network File System (NFS) is a mechanism for storing files on a network.
Preview Code
{"Content":"NFS - Network File System","Description":"Network File System (NFS) is a mechanism for storing files on a network.","category":"Features",
diff --git a/dev/features/Features/wsl/index.html b/dev/features/Features/wsl/index.html
index e291568e..b27ebac1 100644
--- a/dev/features/Features/wsl/index.html
+++ b/dev/features/Features/wsl/index.html
@@ -1,4 +1,4 @@
- Windows Subsystem for Linux - WinUtil Documentation
Announcement: We are currently not adding any applications to WinUtil and any apps that will be added through a PR will be declined by the maintainer. Announcement: We are currently reworking the docs to use Hugo rather then mkdocs.
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
{
+ Windows Subsystem for Linux - WinUtil Documentation
