The application does not start after the update

[BlackBeard12]

Check version

• I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• I've checked for duplicate open and closed issues by using the search function of the issue tracker

Screenshots of crash/graphical issue, version and options menu

What are your system specifications and configuration?

Windows 10; graphics: RTX 2060; Ryzen 5 3600

How to reproduce the issue

1. Download current updte;
2. After that programm closed and does not start;
   I tried to delete and download new setup but it still not working.
   The application does not start, it does not display in the task manager.

Character build code

No response

[Ciccooz]

Hi, can you access the Documents folder or does it give you an error when you try to do so?

[Yasho1313]

I have exactly the same problem. It doesn't launch. Tried installing an older version of PoB and updating it but after the update it didn't launch.
I'm running Win 11.

[racgraffiti]

same issue here on win11, can't start after update, tried run as admin or install either portable/setup exe

[Ciccooz]

I asked about the Documents folder, because I was having problems to access it (since i uninstalled OneDrive, but the folder was still linked somehow), then i fixed the folder and the PoB now works.

[BlackBeard12]

I have access to the Documents. The problem is with the versions of POB 2.40-2.40.1. The old versions work

[cocoemo]

I am having the same issue, I had POB work and suddenly after the update it doesn't work anymore
I have access to Documents.
I see in the event log error ID 1000
Is there a fix to this?

[Yasho1313]

I asked about the Documents folder, because I was having problems to access it (since i uninstalled OneDrive, but the folder was still linked somehow), then i fixed the folder and the PoB now works.

I have access to the folder and no issues with it.
This is what I get in events:

[Mfortitude26]

I have the same issue.

[zao]

@BlackBeard12 @cocoemo @Yasho1313 @Mfortitude26 The information in that event summary is unfortunately not enough to tell the cause (the offset is just for an abort() call).

Could you please see if you have any crash dumps for Path of Building in %LOCALAPPDATA%\CrashDumps and share them privately with me at @.zao on Discord? They contain the crash details, a small amount of the memory of the process and information about the program flow and the program locations.

[zao]

I've acquired crash dump from some of you now, they were very helpful in narrowing down the problem.

We've got two distinct crashes here, the earlier one where SHGetKnownFolderPath(FOLDERID_Documents, KF_FLAG_DEFAULT, ..)` fails to obtain the true path to the Documents folder when the location is sufficiently krangled by OneDrive malfunction.

The other crash is more insidious - it occurs when the directory exists but is named in a way that cannot be represented in the user codepage. This raises an exception at an unexpected (heh) place that unwinds the startup process into an abort().

One of the causes of the latter is if OneDrive controls the Documents folder but have named it in a localized manner with words in Cyrillic or other scripts sufficiently distant from a system codepage like English (United States).

I don't have any immediate solution or workaround to the second type of bug as the location can't be represented at all to the program and it's computed even if running in Portable mode which stores builds elsewhere.

[racgraffiti]

Hi, it seems my condition is about the onedrive and the document folder. I resolved it by changing back the folder path to username\Documents. Here is a link that I followed:https://learn.microsoft.com/en-us/answers/questions/764490/i-uninstalled-onedrive-but-my-files-are-still-redi
Hope it could be some help.

[Mfortitude26]

Same thing here, the Documents folder in my case was in a different language. Just right-clicked, and changed it to "Documents" without even doing anything about one drive and that worked.

Thank you @zao @racgraffiti