mingw32 has recently been updated to gcc 10 and the corresponding update for mingw64 is in progress on :rhabacker:branches:windows:mingw:win64:gcc10. gcc10 was chosen as an intermediate step because a direct update to gcc11 would require too many package adjustments.
The .exe extension on a filename indicates an executable file. Executable files may, in some cases, harm your computer. Therefore, please read below to decide for yourself whether the win64.exe on your computer is a Trojan that you should remove, or whether it is a file belonging to the Windows operating system or to a trusted application.
Description: Win64.exe is not essential for the Windows OS and causes relatively few problems. The file win64.exe is located in a subfolder of the user's profile folder (normally C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\).Known file sizes on Windows 10/11/7 are 24,064 bytes (50% of all occurrences) or 2,384,574 bytes. There is no description of the program. The program starts when Windows starts (see Registry key: Run, MACHINE\RunOnce, MACHINE\Run, User Shell Folders).The file is not a Windows core file.Win64.exe is able to monitor applications and record keyboard and mouse inputs.Therefore the technical security rating is 82% dangerous; but you should also compare this rating with the user reviews.
If win64.exe is located in a subfolder of "C:\Program Files", the security rating is 46% dangerous. The file size is 829,128 bytes.The program has a visible window. The win64.exe file is a file with no information about its developer. The process is loaded during the Windows boot process (see Registry key: Run, User Shell Folders, MACHINE\Run, MACHINE\RunOnce).Win64.exe is not a Windows system file. It is digitally signed.
Important: Some malware also uses the file name win64.exe, for example Generic PUA NJ (PUA) (detected by Sophos), and Artemis!A843B4B36E4D (detected by McAfee). Therefore, you should check the win64.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.
A clean and tidy computer is the key requirement for avoiding problems with win64. 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.
To help you analyze the win64.exe process on your computer, the following programs have proven to be helpful: ASecurity Task Manager displays all running Windows tasks, including embedded hidden processes, such as keyboard and browser monitoring or Autostart entries. A unique security risk rating indicates the likelihood of the process being potential spyware, malware or a Trojan. BMalwarebytes Anti-Malware detects and removes sleeping spyware, adware, Trojans, keyloggers, malware and trackers from your hard drive.
You must also set the WIRESHARK_TARGET_PLATFORM environment variable to "win64" in order to enable 64-bit support in Wireshark's makefiles. You might want to do this in a batch script in order to save some typing, e.g.
Setting WIRESHARK_TARGET_PLATFORM=win64 tells Wireshark's makefiles to download libraries from the "wireshark-win64-libs" SVN repository instead of "wireshark-win32-libs", and to use the libraries defined in the Win64 portion of config.nmake.
The Win64 build uses the Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) to install necessary CRT DLLs. You must download it yourself and place it in c:\wireshark-win64-libs. You should probably run the installer on your development machine as well. 350c69d7ab