Should I block it?

No, this file is 100% safe to run.

VersionsAdditional versions

1, 3, 5, 0 29.58%
1, 3, 4, 0 11.27%
1, 3, 4, 0 4.23%
1, 3, 3, 0 16.90%
1, 3, 3, 0 4.23%
1, 3, 2, 0 1.41%
1, 3, 0, 0 12.68%
1, 3, 0, 0 4.23%
1, 2, 1, 0 2.82%
1, 2, 1, 0 1.41%
1, 1, 10, 0 2.82%
1, 1, 5, 0 4.23%
1, 1, 4, 0 2.82%
1, 1, 3, 0 1.41%

PE structurePE file structure

Show functions
Import table
advapi32.dll
RegSetValueExA, RegOpenKeyExA, RegQueryValueExA, RegCloseKey, RegCreateKeyExA, RegEnumKeyExA
kernel32.dll
MultiByteToWideChar, WideCharToMultiByte, GetLastError, WaitForSingleObject, SetEvent, CloseHandle, FreeLibrary, Sleep, GetProcAddress, LoadLibraryA, ResetEvent, InterlockedExchange, CreateEventA, CreateFileA, DeviceIoControl, GetSystemDirectoryA, GetLocaleInfoA, GetStringTypeW, GetVersionExA, FlushFileBuffers, CreateThread, GetStringTypeA, LCMapStringW, LCMapStringA, WriteConsoleW, GetConsoleOutputCP, WriteConsoleA, SetStdHandle, HeapSize, InitializeCriticalSection, GetOEMCP, GetACP, HeapAlloc, HeapFree, RaiseException, RtlUnwind, HeapReAlloc, VirtualAlloc, GetModuleHandleA, GetThreadLocale, GetCurrentThreadId, GetCommandLineA, GetProcessHeap, TerminateProcess, GetCurrentProcess, UnhandledExceptionFilter, SetUnhandledExceptionFilter, IsDebuggerPresent, DeleteCriticalSection, LeaveCriticalSection, EnterCriticalSection, VirtualFree, HeapDestroy, HeapCreate, ExitProcess, WriteFile, GetStdHandle, GetModuleFileNameA, TlsGetValue, TlsAlloc, TlsSetValue, TlsFree, InterlockedIncrement, SetLastError, InterlockedDecrement, SetHandleCount, GetFileType, GetStartupInfoA, FreeEnvironmentStringsA, GetEnvironmentStrings, FreeEnvironmentStringsW, GetEnvironmentStringsW, QueryPerformanceCounter, GetTickCount, GetCurrentProcessId, GetSystemTimeAsFileTime, SetFilePointer, GetConsoleCP, GetConsoleMode, GetCPInfo, IsValidCodePage
ole32.dll
CoInitialize, CLSIDFromProgID, CoCreateInstance, CoUninitialize
setupapi.dll
SetupDiDestroyDeviceInfoList, SetupDiEnumDeviceInfo, SetupDiGetClassDevsW
user32.dll
EnumDisplaySettingsA, wsprintfA, EnumDisplayDevicesA, ChangeDisplaySettingsA
version.dll
GetFileVersionInfoA, GetFileVersionInfoSizeA, VerQueryValueA
Export table
FinalizeHotkeyDll
FocusItem
GetCurrentItem
GetDisplayItemInfo
InitializeHotkeyDll
SelectItem

FnSpace.dll

FnSpace Module by TOSHIBA CORPORATION (Signed)

Remove FnSpace.dll
Version:   1, 2, 1, 0
MD5:   9082bf97c8d6027ff3e405bdde38c9f1
SHA1:   b412b56e2897dfa635e43b99b8ef2e8da73a17e6

Overview

fnspace.dll is loaded as dynamic link library that runs in the context of a process. The assembly utilizes the .NET run-time framework (which is required to be installed on the PC). The file is digitally signed by TOSHIBA CORPORATION which was issued by the VeriSign certificate authority (CA).

DetailsDetails

File name:fnspace.dll
Publisher:TOSHIBA Corporation
Product name:FnSpace Module
Typical file path:C:\Program Files\toshiba\flashcards\hotkey\fnspace.dll
File version:1, 2, 1, 0
Size:66.84 KB (68,440 bytes)
Certificate
Issued to:TOSHIBA CORPORATION
Authority (CA):VeriSign
Effective date:Thursday, April 22, 2010
Expiration date:Saturday, April 23, 2011
Digital DNA
File packed:No
Code language:Microsoft Visual C# / Basic .NET
.NET CLR:Yes
.NET NGENed:No
More details

Windows OS versionsDistribution by Windows OS

OS versiondistribution
Windows 7 Home Premium 48.44%
Windows 8 20.31%
Windows 7 Ultimate 7.81%
Windows 8 Pro 7.81%
Windows 7 Professional 4.69%
Windows Vista Home Premium 3.13%
Windows 8.1 1.56%
Windows 8 Single Language 1.56%
Windows 7 Starter 1.56%
Windows 7 Enterprise 1.56%
Windows 7 Home Basic 1.56%

Distribution by countryDistribution by country

United States installs about 54.69% of FnSpace Module.

OEM distributionDistribution by PC manufacturer

PC Manufacturerdistribution
Toshiba 98.77%
Acer 1.23%
Should I remove It? Clean your PC of unwanted adware, toolbars and bloatware.

Download it for FREE