Sannpy drivers wont finish downloading indexes

updated

Tron is a script that Fights for the User. It was created to automate a number of functions and utilities in order to remove malware and bloatware, repair damaged operating systems, update old versions of very common applications, free up drive space by clearing out caches, and more. By consolidating and automating these tasks into a single execution it saves a lot of time and makes the whole process a lot more efficient.

Users are STRONGLY ENCOURAGED to read through this documentation before running Tron under penalty of mockery. The Tron subreddit has a long and glorious tradition of pointing out when people don't read the documentation so it's in your best interests to read all of the documentation before you pull the trigger.

Tron is a collection of programs, tools, utilities, and Windows functions that are scripted together. It is designed to remove malware and bloatware, repair damaged operating systems, update old versions of very common applications, free up drive space by clearing out caches, and more. By consolidating and automating these tasks into a single execution it saves a lot of time and makes the whole process a more efficient.

Tron's intended goal is to take a badly-running Windows PC (bloated, infected with malware, neglected, etc) and automate about 85% of the work involved in getting it to run well again. There is nothing Tron does which you couldn't do on your own without it. Tron's real power is in its automation and the breadth of tools that it uses to achieve its intended goal.

While Tron can do a lot of good things for an affected PC, it is important to know that Tron is not a miracle cure-all.

• Tron is not a data recovery tool. It cannot recover files that were deleted or otherwise lost due to system failure or hardware failure.
• Tron is not a decryption tool. It cannot recover encrypted data such as files from an encrypted hard drive where you forgot the key, or if your computer was affected with ransomware. (Tron CAN remove the ransomware from your computer, but once your files have been encrypted the damage will have already been done.)
• Tron cannot solve bottlenecks that are inherent to your computer's hardware configuration. If your hardware is old, slow, or damaged, Tron cannot fix that.
• Tron is not a routine or preventative maintenance tool. As stated, the purpose of Tron is to automate a number of processes in order to get a badly running and/or compromised Windows PC back to a point of functionality again without having to reinstall the operating system. Running Tron to "clean up" a fresh Windows installation and/or as regular maintenance tool on a machine that is running within a reasonable definition of "normally" is not what Tron was intended for and is a tremendous waste of time and energy.
• Tron is not a system optimizer.
• Tron is not a benchmark utility.
• Tron is not a stress test utility.
• Tron will not resolve driver issues (e.g., corrupt or missing drivers).
• Tron will not clean or repair your system registry.

Tron is broken down into ten (10) distinct stages. A full execution of Tron will go through Stages , but individual stages can be run by themselves if you wish. (For example, you can choose to run only Stage 3 and nothing else.) For a full breakdown of Tron's actions for any given stage click on Details of Every Action Taken in the sidebar at right. In brief:

Stage 0: Prep
Checks out the environment in which Tron will be running, performs a few very basic housekeeping tasks to help Tron run smoothly, and gives you a possible path to resurrection should Something Bad happen.

Stage 1: Tempclean
Cleans out a buttload of cache files to free up space on your system.

Stage 2: De-bloat
Uninstalls a myriad of well-known and rarely-liked bloatware in order to free up space on your system and (often) give you a bit of a performance boost.

Stage 3: Disinfect
Runs multiple anti-malware utilities to seek and destroy most malware.

Stage 4: Repair
Checks and attempts to repair permissions issues, your operating system, and the basic structure of your hard drive.

Stage 5: Patch
Updates several very common third-party apps (if they're already installed on your system), and installs any pending Windows updates.

Stage 6: Optimize
Resets your Windows page file and defragments your hard drive (automatically disabled if you're running an SSD).

Stage 7: Wrap-up
Sends a job completion email (if configured to do so), saves a log of its activity, and reboots the system (if the flag was set at launch).

Stage 8: Custom Scripts
Tron will execute any custom batch scripts installed in the appropriate folder. See Executing 3rd-Party Custom Scripts for full details.

Stage 9: Manual Tools
These are additional tools that are included with Tron but aren't actually run automatically with Tron because they don't support command line use, can't be automated, and/or are only useful in very specific circumstances.

1. BACK UP YOUR DATA. This is just a good practice to get into even without Tron. While Tron does nothing that directly affects your data and thousands upon thousands of instances of Tron have been run without any user data problems, there are no guarantees in life and it is ALWAYS better to be safe than sorry. External USB hard drives are cheap and you can use a program such as Macrium Reflect Free to clone your entire startup drive to that external drive so you'll have a complete copy of all your data in the event that Something Bad happens.
2. Pick a time where you won't need your PC for several hours. A good rule of thumb is to launch Tron when you're ready to go to bed, allowing Tron to run on your computer overnight.
3. Download the latest version of Tron through any of the available Download links. You will be downloading an EXE file (a Windows program) but don't run it yet, just download it. If your computer is so affected that you can't download it, you can download it to another PC and copy it to your PC via a USB drive or similar means.
4. If you have any Windows Updates waiting to be installed, let those install. Reboot if necessary. Once the updates are complete, shut down all running apps.
5. If you have any antivirus software installed, temporarily disable all active scanning functions. This can usually be accomplished via a tool in your system tray (next to the clock) but sometimes you may have to launch your antivirus app and turn it off from there. Make sure you disable it "manually" or "indefinitely", which is to say you want it off until you specifically turn it back on again.
6. Make sure you're plugged into an AC power source. This is doubly important if you aren't running a laptop or tablet.
7. Drag the EXE file you downloaded onto your desktop then double-click on it to run it. (Windows 10 users may get a warning about it being an unsigned app. This is normal and you can allow the EXE file to run.) When it's done you should have two folders on your desktop called and .

You are now ready to run Tron.

• The ideal Tron environment is a system that's functional enough to run while "normally" booted (i.e., not in Safe Mode), be able to open an elevated Command Prompt window, and has an active and functional internet connection. This is where you should always make a first attempt to run Tron. Sometimes Tron won't run in this environment due to compromises and issues that already exist in the system, in which case you should try
• the next-best environment, which is a system that meets the above criteria except for the active and functional internet connection. Without an internet connection you won't have access to the absolute latest bloatware and malware removal lists, but you'll have the lists that are included with Tron which should be enough to at least get your system stabilized. Again, if Tron won't run properly in such an environment due to a compromised system, then try
• the next-next-best environment which is a system that can only be used while booted in "Safe Mode with Networking". If Tron still has issues running in this environment, then try
• the "bottom rung" environment which is a system that can only be used while booted in plain "Safe Mode" (no networking).

When running Tron, keep this hierarchy in mind. If you're running Tron while "normally" booted and Tron crashes, quits, or otherwise misbehaves, you may have a situation where something on your system is actively trying to stop Tron from doing its job. To address this, go down one step; disconnect from your network and try again. If that doesn't work, go down another step by booting into "Safe Mode with Networking". When you're able to successfully run Tron without being in a "normal" boot state, then your next step would be to return to a "normal" boot state and run Tron again.

If at any point Tron is interrupted during its execution (e.g., the Command Prompt crashes, the PC crashes, there's an unexpected power cut, etc) you can simply re-launch Tron and it will resume at the beginning of whatever stage it was running when it was interrupted.

Tron (and its stage-specific scripts) can be run in two different ways: you can launch the script directly from Windows Explorer, or you can launch it through an elevated Command Prompt window.

Launching it directly from Windows Explorer is faster and easier but you can't set any switches; Tron will run in its default mode, performing all tasks according to its programming. Also, if there are any errors which cause the script to abort, Tron's window will disappear and you may not have a chance to see the error message. To launch Tron directly, right-click on the Tron batch file and select "Run as administrator" (screen shot) If you're running an OS that has User Account Control enabled, Windows will ask your permission to run and you should allow it by clicking "Yes". If the Command Prompt window opens and then immediately closes, that means you have encountered a random-seeming bug in the Windows command line. If you experience this then you cannot run Tron directly from Windows Explorer and must run it through an elevated Command Prompt window.

Launching Tron through an elevated Command Prompt window is a bit more complicated, but you can set switches to modify Tron's default behavior and you'll be able to see any error messages that may appear as the window won't disappear afterwards. It also avoids the potential for the aforementioned random-seeming bug to appear. To launch Tron through an elevated Command Prompt window, use Windows' search utility to locate the Command Prompt (www.cronistalascolonias.com.ar), then right-click on it and select "Run as administrator". (If you're using Windows 10, you can launch an elevated Command Prompt window directly by pressing WINDOWS-R to bring up the "Run" window, then type and press SHIFT-CONTROL-RETURN.) If you're running an OS that has User Account Control enabled, Windows will ask your permission to run and you should allow it by clicking "Yes". In the resulting Command Prompt window, type the following exactly:

Press RETURN, then type:

If you want to set any switches (see COMMAND-LINE USE) then you should add a SPACE after and enter any switches you want, adding a space between each switch as needed. Press RETURN to launch Tron.

You can also run just a specific stage rather than the full Tron package in the same way. To launch a specific stage directly from Windows Explorer, right-click on the appropriate stage-specific batch file and select "Run as administrator". As before, if the Command Prompt window opens and then immediately closes, that means you have encountered a random-seeming bug in the Windows command line. If you experience this then you cannot run the stage-specific batch file directly from Windows Explorer and must run it through an elevated Command Prompt window.

To launch a specific stage through an elevated Command Prompt window, use Windows' search utility to locate the Command Prompt (www.cronistalascolonias.com.ar), then right-click on it and select "Run as administrator". (If you're using Windows 10, you can launch an elevated Command Prompt window directly by pressing WINDOWS-R to bring up the "Run" window, then type and press SHIFT-CONTROL-RETURN.) If you're running an OS that has User Account Control enabled, Windows will ask your permission to run and you should allow it by clicking "Yes". Type the following exactly:

Press RETURN, then type the appropriate command to launch the stage-specific batch file:

Etc. It is important that your working directly be when you run the script or it may not run properly. When the stage-specific script has finished running your new working directory will likely be so if you wish to run an additional stage-specific script you'll need to go up one level to before running the next script.

Do not use your computer while Tron is running. Do not stop Tron from running so you can work with your PC, then restart Tron when you are finished. Tron is meant to be launched and allowed to run from start to completion in one session.

The only interaction required is clicking "scan" in the MalwareBytes window when it launches in Stage 3. Otherwise the script runs completely autonomously and does not require user input. At the end you will see a red, green or yellow background. Green means no errors, Yellow means a warning was triggered (usually "no Internet connection detected"), and Red means an error was detected. All output is logged to by default.

A Note About Tron "Freezing"

One of the most common questions we see is about Tron seemingly freezing in the middle of its run. In most cases this is caused by the user clicking somewhere inside the command window while Tron is running. This has the unfortunate side effect of "freezing" Tron; it will complete the step that it was on when the window was clicked on, but it won't proceed to the next step.

Look at the title bar of the Command Prompt window. If it says "Administrator" then the process has not frozen, but if it says "Select Administrator" then you've clicked inside the Command Prompt window and Tron has frozen (example). If "Select Administrator" is seen then press RETURN; "Select" should disappear from the title bar and Tron should resume its progress.

If you don't see "Select" in the title bar and Tron is seemingly frozen, then it's most likely that Tron is working on one of the functions that takes more time than others. These longer functions include the de-bloat process in Stage 2, the virus removal in Stage 3 (which includes several different antivirus engines), the SFC (System File Checker) and/or DISM (Deployment Image Servicing and Management) check in Stage 4, or the defragmentation in Stage 6 (for spinning disks only; SSD's are automatically exempt from defragmentation). All of these actions take time to complete and are primarily disk-bound. meaning that systems with slower hard drives and/or lots of files will take longer, potentially several hours to complete just that particular stage.

Why is Tron so big?

I spent many years working overseas where there was no reliable Internet connection, or it was throttled/capped so badly it was unusable. So I built Tron to run completely standalone (e.g. from a thumbdrive or something). Of course, if you do have an Internet connection Tron automatically downloads updates to the de-bloat lists, SSD identifier list (for SSD detection), Sophos engine signatures, etc. But each release is built to run completely standalone.

How long will Tron take to do a complete run?

Typical run-time is hours, sometimes longer, sometimes quicker, depending on how healthy the system is. Best advice is to run it before going to bed and forget about it till the morning. "Set it and forget it."

Why is Tron so slow?

Yes, Tron is slow. The current record for longest run-time was set by /u/MCGamer at 89 hours. Many of Tron's functions are quick and painless even on the slowest of systems, but Tron does include functions that are resource-intensive and can take several hours to complete. These longer functions include the de-bloat process in Stage 2, the virus removal in Stage 3 (which includes several different antivirus engines), the SFC (System File Checker) and/or DISM (Deployment Image Servicing and Management) check in Stage 4, or the defragmentation in Stage 6 (for spinning disks only; SSD's are automatically exempt from defragmentation). All of these actions take time to complete and are primarily disk-bound. meaning that systems with slower hard drives and/or lots of files will take longer, potentially several hours to complete just that particular stage.

What can I do to speed up Tron?

My personal philosophy towards system cleanup is to use more time to "do it right" rather than take shortcuts to "do it quick". With Tron, it's almost always worth letting it run through the full process because 99 times out of the system runs better when it's done. Of course, there are times where expediency is called for and in those cases you can use the command line switches to skip certain portions of Tron at the expense of quality/depth of cleaning. You can also choose to run just a single specific stage of Tron if you wish, although again it comes at the expense of quality/depth of cleaning.

How do I use the command line switches?

Open a Command Prompt window as an administrator and navigate to your 'tron' folder. Once there, type 'tron' followed by a SPACE and then whatever switches you want, with each switch separated by a SPACE, then hit RETURN to begin. For example, if you want tron to skip all virus scans and defragmentation, then you would type 'tron -sa -sd'. Note that if Tron is interrupted (due to a crash or reboot, for example) those switches will remain operational when you relaunch Tron.

Can I run only a certain part of Tron? I only want to de-bloat my computer, for example.

Yes, you can do this. The easiest way to do it is to navigate to your 'tron\resources' folder in Windows Explorer. In there you'll see folders for each stage; stage_1_tempclean, stage_2_de-bloat, etc. Open the appropriate folder and locate the similarly-named batch file. Right-click on that batch file and select "Run as Administrator". If all goes well you'll see a Command Prompt window open and the selected script will execute. If you just see a Command Prompt window flash open and close immediately then you've run into the random-seeming bug which means you'll have to run the batch file manually. To do this, open a Command Prompt window as an administrator and navigate to your 'tron\resources' folder. In there you'll see folders for each stage; stage_1_tempclean, stage_2_de-bloat, etc. Type the name of the folder, followed by a backslash, followed by the similarly-named batch file within. For example, if you want to run the de-bloat script then you would type 'stage_2_de-bloat\stage_2_www.cronistalascolonias.com.ar' and press RETURN.

How do I know Tron won't do something sketchy to my system?

You can't. Caveat emptor applies when running software written by strangers on the Internet. However, you can have reasonable trust that it's built in good faith and does only what it claims to for a few reasons:

1. All code is open-source and available on Github under the MIT license. Everything is heavily commented so if you want to see exactly what it's doing you can go to Github (or crack open the various files with a text editor) and look through it yourself.

2. The code is viewed constantly by the community and it would be difficult to hide something malicious in it.

3. If anything malicious was found, the project reputation would be ruined and someone would just fork Tron to a clean version and carry on from there.

Tron does rely on some third-party tools for heavy lifting so those must be trusted as well, but they're pretty well-known in the PC tech/IT space so there shouldn't be any surprises there.

The bottom line is you can never fully trust any software you didn't write yourself, but you can run Tron with reasonable certainty that it's doing what it claims to be doing and doesn't try any funny business. If you're interested, you can read my personal development philosophy.

Does Tron delete any files from my computer?

This is more complicated than a simple yes/no response can allow. Several of Tron's tools will delete files as a matter of course; the Tempclean stage, for example, will delete tons of cache files from your system, potentially freeing up gigabytes of space. But these cache files aren't "important" in the common term. Cache files aren't your pictures, your MP3s, your documents, etc. They're code and pictures from web sites, scratch files created by programs, and things like that. They're files that will be recreated without error or consequence if they're needed again, and never missed if they're not needed again. However, other tools (for example, those employed in the Disinfect stage) can potentially delete files that are important to you IF they're infected. You may have an application on your computer which is secretly a trojan, or a picture which may have an embedded virus in it, and after the Disinfect stage is complete that application or picture may have been deleted because of that infection. As long as your files aren't secretly hiding some malicious code and you've made a backup before running Tron (just in case), you can safely assume that Tron will not randomly delete your important files.

What do I do after Tron is finished?

Restart your computer and see if things are working better for you. If you're satisfied you can delete the EXE file you downloaded and all of the folders and files created by running that EXE file. You can also delete the Tron logs (by default located at ) though it's a good idea keep the log file for awhile just in case you notice something weird.

Why has Tron been cleaning Internet Explorer for a really long time?

This is a known issue with some Windows builds and is not specific to Tron as the IE cleanup tool is actually part of Windows itself. Part of the temp file cleanup process involves cleaning Internet Explorer v7 and later but in some cases, if Internet Explorer had NEVER been run before, then the IE cleanup tool can hang. If the IE cleanup takes more than about five minutes then it's safe to close the IE cleanup process via Task Manager. Tron will continue on with the next step.

During Stage 2 there's a message along the lines of "ERROR: Shutting down". Why?

This is safe to ignore. It is a known bug for which we haven't yet found a workaround. It means that when a program was removed it triggered the "computer needs to reboot in order to finish removal" flag. This means Windows will not remove any other programs until the system reboots. This doesn't affect anything else in Tron so the recommendation is to just to ignore it and let Tron finish, then manually remove whatever is left over when it's done.

Why does the computer sometimes reboot in the middle of Stage 2?

This is a known bug that I haven't found a solution for yet. Some programs hard-force a reboot when uninstalled via the command line and there's no way to cancel, disable, or prevent it. There's also no way to know beforehand which programs cause this to happen (Toshiba apps seem to cause it more frequently). As a workaround, you can either skip the de-bloat stage or just let Tron pick up where it left off by relaunching it after the computer reboots.

MalwareBytes doesn't auto-scan?

Part of the reason is that MalwareBytes has anti-automation measures built into the interface, so the next-best solution is to just install it and continue on so the script doesn't hang waiting for user input. The main reason however is that I've spoken with the MalwareBytes CIO on the phone a few times and in person and he agreed let us use the free version in the manner we currently do (install, but leave scanning and updating up to the tech to manually execute). They're being very generous allowing us to use it at all so to honor their wishes MalwareBytes will remain a manually-executed function.

MalwareBytes is installed?

Yes. MalwareBytes doesn't have a portable version so MalwareBytes is installed as part of Stage 3: Disinfect. Click "scan" in the window that appears, and when it's finished you can safely remove it if you don't want it on the system. Additionally, running with the switch will have Tron self-destruct and remove all files from the system (excepting MalwareBytes; however this is in the pipeline to be removed with the switch). Logs are left intact in the default run location ().

Tron seems to have stalled. The cursor is twirling and there's an error saying it can't access (or some other file).

Tron is not stalled, do not cancel it. By default Tron hides most scanner output to increase scanning speed and only reports locked system files it can't access; www.cronistalascolonias.com.ar, www.cronistalascolonias.com.ar, and many other files of this nature will not be accessible to Tron. This is normal and it's safe to ignore these errors. If you want to see the FULL output while scanning you can use the (verbose) switch, but note that this will greatly increase Tron's run time.

Why is defrag taking a very long time?

Defrag is very disk I/O intensive and unfortunately there's no way to speed it up. Additionally, from Piriform often "hangs" around %, then suddenly speeds up. I think this is because of a bug in how they calculate estimated run times. TL;DR is just wait and let it finish. Just be patient.

Tron doesn't detect my SSD and attempts defrag

Tron uses from the project (the drive list is automatically updated at runtime if an Internet connection is detected) and automatically detects and skips defrag on SSDs. Occasionally however a new SSD hasn't made it into the list yet and it will run a defrag. No, your SSD isn't damaged by running defrag. But if you're concerned you can force Tron to always skip defrag by using the switch.

When I launch Tron the command window opens, then immediately disappears.

There is a weird bug in Windows where command line programs or scripts will just randomly appear and then close. There isn't a good solution yet, but the workaround is to open an elevated Command Prompt window and run Tron from there. See Basic Tron Execution for full instructions.

I ran Tron but my problem is still happening. Why didn't Tron fix it?

If you're still having an issue after Tron, it may fall into the ~15% of things Tron can't fix automatically. Posting the issue to /r/TechSupport can lead to a good solution.

Tron (or parts of it) just won't run. I even restarted and tried again.

Some malware specifically looks for anti-malware and will delete or disable them if found. As per #5 of the Preparation instructions, you should disable any A/V before running Tron.

My computer restarted in the middle of Tron. I'm back at the desktop but nothing is happening. Is Tron done?

If the computer reboots during Tron, just re-run as an Administrator and it will pick up where it left off. This often happens during Stage 2.

Why not just use Ninite or Ketarin to auto-download tools at runtime?

A lot of people suggest Ninite or Ketarin or some other tool/script as a way to reduce Tron's size and ensure we're always on the latest versions of subtools, but the usefulness of Tron being fully stand-alone outweighs the small extra effort it takes to keep everything updated. By including the things we need within the Tron package there is control over exactly what actions are taken.

As far as using something like Ketarin to make a custom update script, it's mainly because I could not for the life of me figure out Ketarin's interface and don't have time to learn another language, and besides that, download URL's change frequently and Tron uses so many sub-tools it'd be a separate project just to build and maintain an update script. All that said, if you want to build an update script for me, I'd be happy to integrate it into the project.

Why don't you bundle WSUS offline updates with Tron?

As of v, Tron supports using bundled WSUS (Windows Server Update Services) Offline updates. See the instructions for information on how to supply the update packages.

Can I run Tron from a boot disk or PE environment?

Short answer: no.

Long answer: Tron runs a lot of tools that automatically target (typically ), and nearly all of those tools don't have an option to specify a different target drive, which is what you'd need to run it from a PE environment. Additionally, Tron depends on a lot of system variables that are only present on a live system and wouldn't exist or would be incorrect in a PE environment.

Why is Tron written in batch? Why not Powershell?

A lot of people seem to get hung up on this. Ultimately it doesn't matter what language Tron is written in; what matters is that it works for its intended purpose, which it does. It could be written in Perl/C++/Go/etc and as long as it accomplishes the job.

The actual rationale behind why batch was chosen (yes, chosen) is this: On an infected or broken system, the Windows engine is the lowest common denominator and as such, unless the system is severely broken, it will always just work. In contrast, there are many cases where Powershell won't run (broken), isn't installed (XP/), scripting is disabled by default (Vista and up), or one of its very many dependencies are broken. While it may be more work to write Tron in batch, it's worth it because it has a much higher chance of just working. For Tron, consistent reliability across diverse environments is more important than extra features.

All that being said, we'll likely move to a pure PowerShell implementation at some point in the future when XP support is deprecated. I'm a big fan of it (Tron's deployment script is written in Powershell) and would like to take advantage of the extra power and flexibility it offers.

Why not build a Chocolatey package?

It's too much work and the author doesn't have the time. A few people have built Chocolatey packages on their own; do a search in /r/TronScript and you should find some floating around.

Why use Tron rather than just reformat and reinstall?

Most support-minded people (especially those in Enterprise shops) have the mentality that the best solution to an infection is to blow the box away and start from scratch with the latest master image, and Tron's author is in agreement. However, while that's great in places where a master image is available, the reality is that there are a lot of scenarios where:

• There is no master image (small business, personal machine, etc);
• Bandwidth for downloading all of the required system updates and software is too slow/limited;
• The machine is too specialized;
• The machine has legacy software that cannot be readily replaced/reinstalled; or
• It would take significantly more effort to back up user data, blow the machine away, re-install Windows, hunt down drivers, restore user data, then sit down with the owner and get the system set up just like it was before.

Tron is intended for situations where it makes more sense to try for recovery before resigning to a rebuild from scratch.

After running Tron, my antivirus is reporting that malware has affected SettingsModifier:Win32/HostsFileHijack. Did Tron infect my system?

Assuming your copy of Tron was downloaded from an official source, the short answer is no. More recent versions of Windows 10 treats ANY modification of the hosts file as malicious. Part of tron's task list is to maintain privacy by disabling Microsoft's telemetry via an otherwise-harmless modification to the hosts file, but Microsoft has decided that blocking their ability to spy on users is "malicious" so you get this warning.

After running Tron, my (HARDWARE) no longer works properly. Did Tron break my system?

The drivers for your device were most likely removed during the de-bloat process. It is common for bloatware publishers to bundle their software with useful software and this can include device drivers. Removing the bloatware would therefore remove the device driver, in whole or in part. The simplest solution here is to visit the web site of the manufacturer of your device and download/reinstall the drivers for your device(s). Alternately, use a driver installer tool such as Snappy to reinstall the drivers.

After running Tron, my (SOFTWARE) no longer works properly. Did Tron break my system?

There are three possibilities here. First, it's possible that the software you're referring to was infected with malware and therefore deleted during the antivirus stage. Second, if you're running "cracked" software it's possible that the crack was identified as malicious and therefore deleted during the antivirus stage. And third, if your software was identified as bloatware, it's possible that the software was deleted during the de-bloat stage. The solution to all of these issues is the same: reinstall your software, revert to your last Windows restore point, or restore your PC from your backup.

How do I remove all traces of Tron after running it?

Delete the Tron EXE file that you downloaded, the and folders that were created when you ran the Tron EXE file, and the folder at the root level of your startup drive. Uninstall MalwareBytes. Use a registry cleaner (such as CCleaner) to clean out any orphaned registry entries. Empty trash, reboot, and the world will never know.

Where did Tron come from? (aka, "About the Author")

Redditor /u/vocatus created Tron in At the time he was fixing a lot of PCs for friends and family and got tired of hitting NEXT on various cleanup and repair tools. While proprietary (and often expensive) repair tools were available commercially, he was surprised to discover there wasn't any consolidated automation tool like Tron already in existence. That gave him the motivation to write it and release it to the public. Over the years he's improved it through his own efforts and with input from the /r/TronScript community.

Currently /u/vocatus is in the US Army Reserve. Prior to that he was with the NSA for four years, holding the same position and privilege access level as Edward Snowden, coincidentally. In he wintered in Antarctica with the National Science Foundation as the station network engineer and as a member of the GSAR (Glacier Search And Rescue) team. As of this writing he lives and works in the private sector in Phoenix, AZ.

To download Tron

1. Primary Method: Download a self-extracting EXE file from one of the mirrors:

2. Secondary Method: The BT Sync key is no longer published because it was having issues with large swarms (failed to replicate reliably). You can get the key from an old thread or just download from one of the static pack mirrors instead.

3. Tertiary Method: Connect to the SyncThing repo (instructions) to get fixes/updates immediately. This method is IN TESTING may not be reliable.

4. Quaternary Method: All of the source code for Tron is available here on Github Note that this doesn't include many of the utilities Tron relies on to function. If you want to view the code without downloading a ~MB package, or want to contribute to the project, Github is a good place to do it.

contains SHA checksums for every file and is signed with the author's PGP key (0x07df82aa2; included). You can use this to verify package integrity.