Try now

Program info

Estimated safety rating

 winpkg.exe

winpkg.exe may be a dangerous program, according to an automatic analysis of the program's operation. It triggers too many of the "probable danger" flags detailed bellow. It is yet unknown if winpkg.exe is malware or an ok program that doesn't cause harm the PC. Please be careful with this application.

Executable file path

 C:\Windows\Temp\NET\WinPKG.exe

Usually, the default filename and folder where this program is stored is
C:\Windows\Temp\NET\WinPKG.exe.

MD5 hash of the executable file

 b3a88bbd3509a3550763e92f867df616

The MD5 checksum for this file is b3a88bbd3509a3550763e92f867df616.

Is running as a service

 No

This program is NOT registered as a Windows service. This is good.

Is a 32 bit executable file

 Yes

This app runs as a 32-bit program. It can not use the full set of features of nowadays' PC processors. This is quite normal because the authors did not bother to upgrade it to 64-bit code.

File description

 Package Installer for "All in One Runtimes"

The description extracted from the program is Package Installer for "All in One Runtimes".

File version

 1.0.0.13

File version extracted from the file 1.0.0.13.

Manufacturer

 Sereby Corporation

Company name Sereby Corporation.

Copyright

 (C) 2014-2016 - www.Sereby.org

Intellectual property rights notice (C) 2014-2016 - www.Sereby.org.

Has valid windows

 No

This executable does NOT have visible elements of user interface. This is usually a bad sign.

Is an encrypted file

 Yes

The machine code of this executable appears to have been compressed or encrypted so it can not be quickly decompiled.

Potentially dangerous functions

 Yes

Some unusual functions of the Operating System have been used, such as functions for intercepting the keyboard. We recommend you to read more about this program.

Digitally signed

 No

The digital signature is missing from this program. The maker did not bother to sign it. This is probably bad.

Can be uninstalled

 No

This program does NOT have a removal routine set up in registry.