Jump to content
You must now use your email address to sign in [click for more info] ×

Beta for Windows not running


Recommended Posts

Win 10 (upgrade from Win 8), 64 bit...no problems loading exe file...when attempt to run, initial title appears (with blue circle...a hopeful sign), then disappears as if had never attempted to run...tried diff compatability settings, same result.

Link to comment
Share on other sites

  • Staff

Hi Euclid,

 

I'm sorry you're experiencing this problem - we seem to have a lot of reports of this behaviour and we're working very hard to try to track down what is common to these systems so we can establish the problem and fix it. Would you be able to help us by giving some details of your computer - what CPU, graphics card, memory, any virus scanner/firewall software installed?

 

Thanks in advance,

Matt 

Link to comment
Share on other sites

Hi, I'm having the exact same issue. Shows the title window then disappears, never to be seen again.

 

PC Specs:

Windows 10 Pro 64-bit

Intel Core i7-4930K CPU @ 3.40GHz

EVGA GTX 1080 FTW GPU
48gb RAM

750gb SSD

 

Thanks! :)

Link to comment
Share on other sites

  • Staff

That looks fine then. Does your system have a large number of fonts?

 

Do you have any crash reports in the following location :-

%APPDTA%\Roaming\Serif\Affinity Designer\1.0 (Beta)\Crash Reports

 

If so could you please post one for us to look at.

 

Thanks

Link to comment
Share on other sites

I do have quite a lot of fonts. I'll try installing the beta on a machine with the standard amount of fonts for Windows 10 and see if that makes a difference.

 

Here is part of the crash analysis from the latest .dmp file (it doesn't include the Stack_Text section):
 

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\347878d1393f6b869d18d658656f2b60\WindowsBase.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for WindowsBase.ni.dll
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\43226440664fdfb99f9ad60968b2a60c\mscorlib.ni.dll, Win32 error 0n2
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\55717213a974c71f8e82532af3997d5f\PresentationCore.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for PresentationCore.ni.dll
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\f5d6f299601b66b7afc4865aac448cf2\PresentationFramework.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for PresentationFramework.ni.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2
*** ERROR: Module load completed but symbols could not be loaded for Designer.exe
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\8e325c9a2b96c925621b8214b5785cd7\System.Core.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify checksum for System.Core.ni.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
GetUrlPageData2 (WinHttp) failed: 12029.
*** The OS name list needs to be updated! Unknown Windows version: 10.0 ***

FAULTING_IP: 
KERNELBASE!RaiseException+68
00007ffa`68cc1f28 488b8c24c0000000 mov     rcx,qword ptr [rsp+0C0h]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ffa68cc1f28 (KERNELBASE!RaiseException+0x0000000000000068)
   ExceptionCode: e0434352 (CLR exception)
  ExceptionFlags: 00000001
NumberParameters: 5
   Parameter[0]: ffffffff80004005
   Parameter[1]: 0000000000000000
   Parameter[2]: 0000000000000000
   Parameter[3]: 0000000000000000
   Parameter[4]: 00007ffa5b780000

PROCESS_NAME:  Designer.exe

ERROR_CODE: (NTSTATUS) 0xe0434352 - 

EXCEPTION_CODE: (NTSTATUS) 0xe0434352 - 

EXCEPTION_PARAMETER1:  ffffffff80004005

EXCEPTION_PARAMETER2:  0000000000000000

EXCEPTION_PARAMETER3:  0000000000000000

EXCEPTION_PARAMETER4: 0

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

MANAGED_BITNESS_MISMATCH: 
Managed code needs matching platform of sos.dll for proper analysis. Use 'x64' debugger.

FAULTING_THREAD:  00000000000002cc

BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS_CLR_EXCEPTION_NOSOS

PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS_NOSOS

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS_NOSOS

LAST_CONTROL_TRANSFER:  from 00007ffa5b85fd71 to 00007ffa68cc1f28

Link to comment
Share on other sites

Just to note, I installed the beta on another Windows 10 machine with an AMD processor and does not have more than the standard amount of fonts installed on it (if that makes a difference) and it works great.

 

PC (laptop) Specs:

Windows 10 64-bit

AMD A10-4600M APU @ 2.30 GHz

AMD Radeon HD 7660G GPU

16 GB RAM

500 GB SSD

 

Hope that helps!

Link to comment
Share on other sites

  • Staff

JDHauger,

 

Thanks for your help with this issue - we believe we have fixed the problem with having a large number of fonts installed and have produced a new build (1.5.0.4 - link in the post at the top of the forum).

 

Hopefully, this will work for you!!

 

Andy.

Link to comment
Share on other sites

  • Staff

1.5.0.2 didn't work at all and kept crashing after splash screen. Just installed 1.5.0.4 and its working now! 

 

Thanks!!

 

Thanks for letting us know. We still have many issues to fix but we will keep the builds coming for you to test ;)

Link to comment
Share on other sites

I am having the exact same problem! I double click short cut and nothing.

Running Windows 8.1

12 g memory

64 bit

not too many fonts

 

I just removed the program and did a fresh download. Still nothing after double clicking shortcut icon.

Link to comment
Share on other sites

Guest Arun Sarkar

Latest built still did not run 

 

with my Win 8.1 64 bit

NVEDIA GeForce 8600GT

4GB Ram

 

:angry:

Link to comment
Share on other sites

Hi, I'm not familiar with computer spec, so I just took note.

Windows 7 Home Premium SP1
Intel® Core
i3-2310M CPU
2.10GHz
RAM 4GB
64-bit OS
 
I'm having the same problem. I've got the shortcut ready on my desktop after downloading the first update. Click on it, and nothing happen, instead an error reporting notification then show up on bottom right corner.
 
I have high hopes on this since I'm no longer wish to use adobe.
Regards from Indonesia
 
Update at 8.15pm (GMT+7) :
After having no luck opening the app; With no intention of fixing the problem, my husband did the System Ninja (he said it's cache cleaner app), he left and I press the delete all junk, and again with no intention of fixing the problem, I deleted some pics on my desktop, and spotted gimp shortcut. I immediately uninstall the keeps-crashing gimp, since I don't need such headache. Done with gimp, I thought maybe give Affinity another try. Nothing happen, no error notification either. So I thought I'll just wait for any reply in the forum. So I went browsing for other stuff.
 
Then I saw the Affinity icon on my taskbar. OMG, it's there, all ready!! I'm not sure which action enables it. Maybe it's the cache cleaner, maybe it's uninstalling gimp. 
 
Now I'm trying to get to know all the functions. I'm super excited, my kids said, "You look very happy Mom" :D
Link to comment
Share on other sites

Hi there,

 

I have had the same problem with my Affinity Beta not loading past the Affinity logo. 

 

The specs of my dell laptop are as follows:

-Windows 10 home V 1511

-Processor: Intel i7-5500u 

-System Type: ACPI 64 Bit x 64 based processor 

-Intel HD Graphics 5500

-Windows Defender V 4.9.10586.0

 

There were also a lot of Intel (driver & other) updates recently. 

 

Thanks :) 

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.