Hitman PRO problem

[Ivan Kr]

When i want to open Affinity Publisher, this is what i get:

Mitigation   ROP
Timestamp    2020-11-14T18:55:21

Platform     10.0.19041/x64 v797 06_5e
PID          244
Feature      001F0A361FBF01B2
Application  E:\Affinity\Publisher\Publisher.exe
Created      2020-08-13T10:03:10
Modified     2020-08-13T10:03:10
Description  Affinity Publisher 1.8.5

Callee Type  LoadLibrary
             ext-ms-win-kernel32-errorhandling-l1-1-0.dll

Stack Trace
#  Address          Module                   Location
-- ---------------- ------------------------ ----------------------------------------
1  00007FFE089EBCEF KernelBase.dll          
2  00007FFE0AFD4973 ntdll.dll               
3  00007FFE0AFBB906 ntdll.dll                __C_specific_handler +0x96
4  00007FFE0AFD10FF ntdll.dll                __chkstk +0x11f
5  00007FFE0AF7B474 ntdll.dll               
6  00007FFE0AFCFC2E ntdll.dll                KiUserExceptionDispatcher +0x2e

7  00007FFDD3FF2140 clr.dll                 
                    803c1900                 CMP          BYTE [RCX+RBX], 0x0
                    0f8592ee3700             JNZ          0x7ffdd4370fdc
                    498d8e30050000           LEA          RCX, [R14+0x530]
                    e947040000               JMP          0x7ffdd3ff259d

8  00007FFDD3FF1DFB clr.dll                  GetMetaDataInternalInterface +0x14b
9  00007FFDD3FF1D09 clr.dll                  GetMetaDataInternalInterface +0x59
10 00007FFDD3FF1C62 clr.dll                 

Loaded Modules
-----------------------------------------------------------------------------
000002448F1A0000-000002448F5DE000 Publisher.exe (),
                                  version:
00007FFE0AF30000-00007FFE0B126000 ntdll.dll (Microsoft Corporation),
                                  version: 10.0.19041.610 (WinBuild.160101.0800)
00007FFDD7870000-00007FFDD78D5000 MSCOREE.DLL (Microsoft Corporation),
                                  version: 10.0.19041.1 (WinBuild.160101.0800)
00007FFE09590000-00007FFE0964D000 KERNEL32.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE088E0000-00007FFE08BA8000 KERNELBASE.dll (Microsoft Corporation),
                                  version: 10.0.19041.572 (WinBuild.160101.0800)
00007FFE08300000-00007FFE08418000 hmpalert.dll (SurfRight B.V.),
                                  version: 3.7.14.797
00007FFDF69C0000-00007FFDF6A94000 atcuf64.dll (Bitdefender S.R.L. Bucha),
                                  version: 1.34.268.0 #0x011f0aa
00007FFE0A4A0000-00007FFE0A54C000 ADVAPI32.dll (Microsoft Corporation),
                                  version: 10.0.19041.610 (WinBuild.160101.0800)
00007FFE0A940000-00007FFE0A9DE000 msvcrt.dll (Microsoft Corporation),
                                  version: 7.0.19041.546 (WinBuild.160101.0800)
00007FFE08F90000-00007FFE0902B000 sechost.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE0A370000-00007FFE0A494000 RPCRT4.dll (Microsoft Corporation),
                                  version: 10.0.19041.630 (WinBuild.160101.0800)
00007FFDD5A10000-00007FFDD5ABA000 mscoreei.dll (Microsoft Corporation),
                                  version: 4.8.4180.0 built by: NET48REL1LAST_B
00007FFE09A40000-00007FFE09A95000 SHLWAPI.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE064C0000-00007FFE064D2000 kernel.appcore.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE040C0000-00007FFE040CA000 VERSION.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFDD3F80000-00007FFDD4A42000 clr.dll (Microsoft Corporation),
                                  version: 4.8.4250.0 built by: NET48REL1LAST_C
00007FFE0A790000-00007FFE0A930000 USER32.dll (Microsoft Corporation),
                                  version: 10.0.19041.610 (WinBuild.160101.0800)
00007FFE08F60000-00007FFE08F82000 win32u.dll (Microsoft Corporation),
                                  version: 10.0.19041.630 (WinBuild.160101.0800)
00007FFE0A9E0000-00007FFE0AA0A000 GDI32.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE08720000-00007FFE08829000 gdi32full.dll (Microsoft Corporation),
                                  version: 10.0.19041.572 (WinBuild.160101.0800)
00007FFE08C00000-00007FFE08C9D000 msvcp_win.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE08CA0000-00007FFE08DA0000 ucrtbase.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFDE3C50000-00007FFDE3C66000 VCRUNTIME140_CLR0400.dll (Microsoft Corporation),
                                  version: 14.10.25028.0 built by: VCTOOLSD15RTM
00007FFDE05F0000-00007FFDE06AD000 ucrtbase_clr0400.dll (Microsoft Corporation),
                                  version: 14.10.25028.0 built by: VCTOOLSD15RTM
00007FFE09500000-00007FFE09530000 IMM32.DLL (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFE0A930000-00007FFE0A938000 psapi.dll (Microsoft Corporation),
                                  version: 10.0.19041.546 (WinBuild.160101.0800)
00007FFDCBDB0000-00007FFDCD3B0000 mscorlib.ni.dll (Microsoft Corporation),
                                  version: 4.8.4250.0 built by: NET48REL1LAST_C

Process Trace
1  E:\Affinity\Publisher\Publisher.exe [244] 2020-11-14T18:55:20
2  C:\Windows\explorer.exe [4492] 2020-11-14T06:18:37
3  C:\Windows\System32\userinit.exe [12484] 2020-11-14T06:18:37 22.9s
4  C:\Windows\System32\winlogon.exe [12544] 2020-11-13T22:11:17
   C:\WINDOWS\System32\WinLogon.exe -SpecialSession
5  C:\Windows\System32\smss.exe [12576] 2020-11-13T22:11:17 181ms
   \SystemRoot\System32\smss.exe 000000f0 00000084 C:\WINDOWS\System32\WinLogon.exe -SpecialSession
6  C:\Windows\System32\smss.exe [532] 2020-11-11T15:43:29
   \SystemRoot\System32\smss.exe
7   [4] 2020-11-11T15:43:28

Thumbprint
952466826a58fa5a213bf88b7d7cd91065fa03dd3cb13166d2217f2cb47242bf

 

 

 

Why?

[Dan C]

Hi @Ivan Kr,

Sorry to see you're having trouble. Can you please confirm for me, where has this information been copied from?

If the app is crashing whilst opening then we're going to require a copy of your latest crash reports to identify this issue.

Please open Windows Run (Windows Key + R) then paste the following string and press OK:

%AppData%\Affinity\Publisher\1.0\CrashReports\reports

In the window that opens, please select the 3 most recently created .dmp files, then upload these to your reply here.
Many thanks in advance!

[v_kyr]

What are ext-ms-win-kernel32-errorhandling-l1-1-0.dll Error Messages?

Dynamic Link Library ext-ms-win-kernel32-errorhandling-l1-1-0.dll Errors

Ext-ms-win-kernel32-errorhandling-l1-1-0.dll is considered a type of Dynamic Link Library (DLL) file. Dynamic Link Library files, like ext-ms-win-kernel32-errorhandling-l1-1-0.dll, are essentially a "guide book" that stores information and instructions for executable (EXE) files - like sapisvr.exe - to follow. These files were created so that multiple programs (eg. Windows) could share the same ext-ms-win-kernel32-errorhandling-l1-1-0.dll file, saving valuable memory allocation, therefore making your computer run more efficiently.

Unfortunately, what makes DLL files so convenient and efficient, also makes them extremely vulnerable to problems. If something happens to a shared DLL file, either it goes missing or gets corrupted in some way, it can generate a "runtime" error message. Runtime is pretty self-explanatory; it means that these errors are triggered when ext-ms-win-kernel32-errorhandling-l1-1-0.dll is attempted to be loaded either when Windows is starting up, or in some cases already running. Some of the most common ext-ms-win-kernel32-errorhandling-l1-1-0.dll errors include:

• Access Violation at address - ext-ms-win-kernel32-errorhandling-l1-1-0.dll.
• Ext-ms-win-kernel32-errorhandling-l1-1-0.dll could not be found.
• Cannot find C:\Windows\System32\ext-ms-win-kernel32-errorhandling-l1-1-0.dll.
• Cannot register ext-ms-win-kernel32-errorhandling-l1-1-0.dll.
• Cannot start Windows. A required component is missing: ext-ms-win-kernel32-errorhandling-l1-1-0.dll. Please install Windows again.
• Failed to load ext-ms-win-kernel32-errorhandling-l1-1-0.dll.
• The application has failed to start because ext-ms-win-kernel32-errorhandling-l1-1-0.dll was not found.
• The file ext-ms-win-kernel32-errorhandling-l1-1-0.dll is missing or corrupt.
• This application failed to start because ext-ms-win-kernel32-errorhandling-l1-1-0.dll was not found. Re-installing the application may fix this problem.

Your ext-ms-win-kernel32-errorhandling-l1-1-0.dll file could be missing due to accidental deletion, uninstalled as a shared file of another program (shared with Windows), or deleted by a malware infection. Furthermore, ext-ms-win-kernel32-errorhandling-l1-1-0.dll file corruption could be caused from a power outage when loading Windows, system crash while loading ext-ms-win-kernel32-errorhandling-l1-1-0.dll, bad sectors on your storage media (usually your primary hard drive), or quite commonly, a malware infection. Thus, it's critical to make sure your anti-virus is kept up-to-date and scanning regularly.

... and so on ...