12 ms·

iwr https://chocolatey.org/install.ps1 | iex cinst -y totalcommander copyq neovim vscode firefox everything sysinternals nirlauncher smplayer vlc git tortoi

iwr https://chocolatey.org/install.ps1 | iex cinst -y totalcommander copyq neovim vscode firefox everything sysinternals nirlauncher smplayer vlc git tortoisegit conemu 7zip paint.net dngrep dbeaver Update-SessionEnvironment git clone https://github.com/W4RH4WK/Debloat-Windows-10 ls Debloat-Windows-10/scripts/*.ps1 | % { . $_ } # YMVV git clone https://github.com/majkinetor/powershell_profile.d gc powershell_profile.d/setup -raw | iex code --install-extension ms-vscode.PowerShell ... Install-Module PSWindowsUpdate # repeat this as long as needs restart Install-WindowsUpdate -AcceptAll Restart-Computer Then I go ad-hoc from there... That is for my daily machine. For specialized machines such as media center etc, the list is different...

Someone1234 7y ago
Running all of those Debloat scripts: - Permanently disables Windows Defender (requires registry changes to re-enable). - Breaks the browser choice window. Skype. Time sync. - Disables services seemingly arbitrarily. - Disables SmartScreen. - Disables both automatic updates and the notification for manual updates. - Sets mouse speed/sensitivity/smoothing/pointer settings(???). - Disables accessibility features. - Reverts the volume slider. My point is, it isn't "debloat" it is a fully opinionated default state for Windows 10, completely arbitrary, likely inconvenient, and potentially dangerous (SmartScreen, Windows Update, etc). Windows may also fail to update after this due to ACL permissions set on some files/registry keys/directories to keep certain features broken. I do not recommend anyone runs this.
- majkinetor 7y ago
  I don't run exactly all, but like I said, YMMV. That said, bunch of people I know run this all the time, me included, and besides some trivial stuff Windows runs at least x2 faster and feels snappier. Those scripts are meant to be inspected and applied. Besides, what kind of engineers are we if we can't fix something done with the script ? You don't recommend experimentation, I can live with that if we don't do work together... Otherwise, perhaps you should try running what looks to you like arbitrary setup and see what path it takes you.
  - Someone1234 7y ago
    You suggested people run: > ls Debloat-Windows-10/scripts/*.ps1 | % { . $_ } So kinda are suggesting people run them all. Plus "run them all then fix all the stuff it breaks otherwise you aren't a true engineer" isn't a particularly strong argument for this. People that know what they're doing don't need these kind of scripts (and would know better than half of what these scripts do anyway). So these kind of scripts pray on those likely not to know enough to fix the issues they cause. But regardless, just don't start posting about how Windows Update never works correctly because you manually set HOST file and ACL privileges that are specifically designed to stop Windows from working in a normal way. You play silly games you win silly prizes.
    - majkinetor 7y ago
      I suggested: > ls Debloat-Windows-10/scripts/*.ps1 | % { . $_ } # YMMV Notice YMMV comment :) So now you made the entire thing about it ... :)

Someone1234 7y ago

Running all of those Debloat scripts: - Permanently disables Windows Defender (requires registry changes to re-enable). - Breaks the browser choice window. Skype. Time sync. - Disables services seemingly arbitrarily. - Disables SmartScreen. - Disables both automatic updates and the notification for manual updates. - Sets mouse speed/sensitivity/smoothing/pointer settings(???). - Disables accessibility features. - Reverts the volume slider. My point is, it isn't "debloat" it is a fully opinionated default state for Windows 10, completely arbitrary, likely inconvenient, and potentially dangerous (SmartScreen, Windows Update, etc). Windows may also fail to update after this due to ACL permissions set on some files/registry keys/directories to keep certain features broken. I do not recommend anyone runs this.

majkinetor 7y ago
I don't run exactly all, but like I said, YMMV. That said, bunch of people I know run this all the time, me included, and besides some trivial stuff Windows runs at least x2 faster and feels snappier. Those scripts are meant to be inspected and applied. Besides, what kind of engineers are we if we can't fix something done with the script ? You don't recommend experimentation, I can live with that if we don't do work together... Otherwise, perhaps you should try running what looks to you like arbitrary setup and see what path it takes you.
- Someone1234 7y ago
  You suggested people run: > ls Debloat-Windows-10/scripts/*.ps1 | % { . $_ } So kinda are suggesting people run them all. Plus "run them all then fix all the stuff it breaks otherwise you aren't a true engineer" isn't a particularly strong argument for this. People that know what they're doing don't need these kind of scripts (and would know better than half of what these scripts do anyway). So these kind of scripts pray on those likely not to know enough to fix the issues they cause. But regardless, just don't start posting about how Windows Update never works correctly because you manually set HOST file and ACL privileges that are specifically designed to stop Windows from working in a normal way. You play silly games you win silly prizes.
  - majkinetor 7y ago
    I suggested: > ls Debloat-Windows-10/scripts/*.ps1 | % { . $_ } # YMMV Notice YMMV comment :) So now you made the entire thing about it ... :)