mirror of
https://github.com/JonasunderscoreJones/WindowsBloatwareRemover.git
synced 2025-10-25 10:49:18 +02:00
Fixed ReadMe again.
Tweaked to make stuff more clear and fixed link issues, etc.
This commit is contained in:
parent
8d66973631
commit
ea33b6f9f5
1 changed files with 3 additions and 3 deletions
|
|
@ -23,8 +23,8 @@ There are two steps to permanently remove Microsoft Edge from Windows:
|
|||
2. A registry key needs to be created to tell Windows to not reinstall the browser after a Windows update.
|
||||
|
||||
The second step is surprisingly the easy part and can be done with only two commands. But running the uninstaller for the edge browser is way trickier than I originally thought, and here is why:
|
||||
- The Windows Powershell has issues finding files that are located within the "Program Files (x86)" directory and all of its child directories, meaning all folders and files within that folder. There seam to be ways to problem (by using a combination of the alias for the x86 directory but not immediately parsing it into the directory path but defining it as a variable first but my countless tries to achieve that were unsuccessful and right now I am way too frustrated from writing powershell scripts (Ps-script is one of the ugliest shell scripting languages I have ever seen))
|
||||
- Programmatically running the executable seams to be impossible. When using the default command line to run the command that runs the executable (or running the program in the powershell from the exact location of the uninstall-executable for edge to avoid the x86 issue) windows seams to not run it correctly but when I, as a user, paste the command and run it manually, it always worked. Either Windows has a built-in function to prevent you from programmatically remove Edge, or I am just a moron.
|
||||
- The Windows Powershell has issues finding files that are located within the "Program Files (x86)" directory and all of its child directories, meaning all folders and files within that folder which, unfortunately, is where the edge executable is located. There seam to be ways to solve that problem (by using a combination of the alias for the x86 directory but not immediately parsing it into the directory path by defining it as a variable first but my countless tries to achieve that were unsuccessful and right now I am way too frustrated from writing powershell scripts (Ps-script is one of the ugliest shell scripting languages I have ever seen))
|
||||
- Programmatically running the executable seams to be impossible. When using the default command line to run the command that runs the executable (or running the program in the powershell from the exact location of the uninstall-executable for edge to avoid the x86 issue) windows seams to not run it correctly but when I, as a user, paste the command and run it manually, it always worked. Either Windows has a built-in function that prevents you from programmatically remove Edge, or I am just a moron.
|
||||
|
||||
But just in case, I am working on a solution, and I will (probably) find one. Since I don't use Windows anymore but have switched over Linux a while ago, this is of course not my highest priority so there might not be any updates and bug-fixing in the near future (I also have no time rn).
|
||||
|
||||
|
|
@ -39,4 +39,4 @@ For everyone else: Microsoft is a master when it comes to slapping bloatware and
|
|||
For real though, I occasionally use Windows virtual machines and despite having a backup that I can easily clone every time I do experiments, etc.., reinstalling a fresh copy of Windows 10 needs to be done from time to time.
|
||||
|
||||
# Donations for new PC
|
||||
Click  (definitely not a Rick Roll) to donate me money so that I can buy a new PC to test this on Windows 11.
|
||||
Click [here](http://jonasjones.me/uwu) (definitely not a Rick Roll) to donate me money so that I can buy a new PC to test this on Windows 11.
|
||||
Loading…
Add table
Add a link
Reference in a new issue