Jump to content

Block Updates with W10 Firewall - Alpha Test


Oops19

Recommended Posts

Posted

Please to not yet download unless you know how to read, edit and fix CMD scripts. You don't want to damage your TS4 installation.

Thank you.

 

 

 

Warning

After download please open the script in an editor and review it or use 7-Zip>View. Running programs with elevated privileges can lead to serious issues. I have no bad intentions and it is open source so please take the time to review it.

"certutil -hashfile Oops19_Firewall.cmd SHA256" should return "7ac14106732bebab2edcf3fa2997eed5fbd903e49299408aeba1c7eb1e39a672"

 

Description

This is a simple script which blocks or allows access to the internet for the Origin updater and TS4. As it blocks internet access for Origin also the TS4 online functions do no longer work.

Today another update was announced and I was not in the mood to install it. Anyhow Origin has no offer to skip it, unless it is offline. Many users have the problem that after an update mods do no longer work. This issue may be avoided with this script. Anyhow at least one (--> TURBODRIVER ?) has to update to the newest version first to test it.

 

If Origin or TS4 is installed at a non-default location or the 32 bit version is used the locations have to be edited in the script - otherwise it partly fails. There is no registry access implemented to check for the proper file locations. After editing the SHA256 value will no longer match.

The script must be run as an administrator to be able to modify the Windows firewall. It can be run as a standard user to test things.

 

Usage

Usage: Oops19_Firewall.cmd [show/rm/allow/deny] [wait]
show ... shows the firewall rules if any.
rm ... removes the firewall rules.
allow ... adds firewall rules to allow access.
deny ... adds firewall rules to block access.
wait ... keeps the window open for 10 seconds to review the output in script mode.

Windows Shortcuts vs. Iteractive Mode

The script supports an interactive mode (right-click, Run as Administrator) but the idea is to create some shortcuts to the script and edit them:

1. Advanced>Run as Administrator

2. Target: ...\Oops19_Firewall.cmd deny wait (or ...\Oops19_Firewall.cmd rm wait)

 

Issues

Do not save it on a network drive as running it there as an Admin may fail.

I tested it locally, hopefully there are not too many issues.

 

 

Any feedback is welcome, like confirmation of SHA256, usefulness, migration to Powershell, etc.

2020-02-03_Oops19_Firewall.zip

  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...