Most antivirus programs identify Microsoft Startup Controller.exe as malware—for instance Kaspersky identifies it as Trojan.Win32.Genome.ssew or Trojan-Spy.Win32.Ardamax.fq, and Microsoft identifies it as Worm:Win32/Thraegisa.A or Worm:Win32/Yosheetsune.A.
The free file information forum can help you find out how to remove it. If you have additional information about this file, please leave a comment or a suggestion for other users.
There is no information about the producer in the Microsoft Startup Controller.exe process.
Description: Microsoft Startup Controller.exe is not essential for Windows and will often cause problems. The Microsoft Startup Controller.exe file is located in a subfolder of the user's profile folder.
Known file sizes on Windows 10/8/7/XP are 90,605 bytes (66% of all occurrences) or 101,376 bytes.
The application has no file description. The program has no visible window. The application starts when Windows starts (see Registry key: User Shell Folders). It is not a Windows core file. Therefore the technical security rating is 64% dangerous.
Important: You should check the Microsoft Startup Controller.exe process on your PC to see if it is a threat. We recommend Security Task Manager for verifying your computer's security. This was one of the Top Download Picks of The Washington Post and PC World.
The following programs have also been shown useful for a deeper analysis: ASecurity Task Manager examines the active Microsoft Startup Controller process on your computer and clearly tells you what it is doing. Malwarebytes' well-known Banti-malware tool tells you if the Microsoft Startup Controller.exe on your computer displays annoying ads, slowing it down. This type of unwanted adware program is not considered by some antivirus software to be a virus and is therefore not marked for cleanup.
A clean and tidy computer is the key requirement for avoiding PC trouble. This means running a scan for malware, cleaning your hard drive using 1cleanmgr and 2sfc /scannow, 3uninstalling programs that you no longer need, checking for Autostart programs (using 4msconfig) and enabling Windows' 5Automatic Update. Always remember to perform periodic backups, or at least to set restore points.
Should you experience an actual problem, try to recall the last thing you did, or the last thing you installed before the problem appeared for the first time. Use the 6resmon command to identify the processes that are causing your problem. Even for serious problems, rather than reinstalling Windows, you are better off repairing of your installation or, for Windows 8 and later versions, executing the 7DISM.exe /Online /Cleanup-image /Restorehealth command. This allows you to repair the operating system without losing data.