>>16440518 pb
Once again: RemoveRestrictions.bat from Mike Lindell Sympossium proves widespread election fraud. Essentially what the script does is switches a voting machine local security to point to a temporary database so nefarious activities can be logged there and leave no trace. Then after the machine reboots, it utilizes the normal database that is on the local hard drive.
Echo off means no output to console
Echo on means output to console, used for debugging
Line by Line
1 Shut off output to console window and set a local variable enableextensions to true
2 types Removing Security Restrictions out to console, when Echo is on
-
sets the configuration for the database, db, to a temp database and silently overwrites the initiatization file. This is the database that the windows local security authority logs all information, metrics, and changes to the system. It is the machines system of records.
-
Overwrites the GroupPolicy for the windows/system32 giving it new authority rules and policies.
-
Modifies the windows registry to force it to accept the new security providers
-
if errorlevel os negative or 0 pause
-
types Critical restrictions disabled when Echo is on, set on line 1, and types Registry value that indicates the current hardening state
-
Modifies Dominion SQL database registry key Hardened variable and forces a Dehardened-WS2016 string to be set.
-
Sets the local machines SQL server socket network library to disable encryption
10 stop the SQL database
11 start the SQL database without encryption
12 starts the SQLServerAgent
Because this is a script, it takes a long time to write and test to get correct. This is only done when one wants to repeat the same tasks on many many machines instead of doing commands by interacting with the mouse and keyboard. Because it tampers with a machines local security on a voting machine it is a crime. In addition, to run a web server on a voting machine is remote access; which is also illegal.
PS
Remember when they lied and said that a technician accidentally erased election information and I proved to them that you just can''t accidentally erase a SQL.Dat file because it would require shutting down database services that lock the file and the person who does that has to be a SQL or Domain Admin to do that. They changed their story the next day and said it wasn't lost after all.