Project

General

Profile

Bug #445

Game Launcher: Unknown bundle setup error: 0x80070002

Added by Backer ascl over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Steam or Launcher:
Launcher

Description

Just tried to install the game, but the launcher fails. Digging around in temp I see the following inside Setup_<longnumber>_Failed.txt (which is the most recent file in temp).


[39E4:3B4C][2016-07-23T08:58:06]i001: Burn v3.10.2.2926, Windows v10.0 (Build 14366: Service Pack 0), path: C:\Users\nb\AppData\Local\Temp\4c1ca9a81e1f40ab868924ea5ce40efc\9654523926e1430b84bd8e2c415e07ee.tmp
[39E4:3B4C][2016-07-23T08:58:06]i000: Initializing string variable 'InstallationFolder' to value '[ProgramFilesFolder]Warhorse Studios\KCD Beta Access'
[39E4:3B4C][2016-07-23T08:58:06]i009: Command Line: '-burn.embedded bpe_570c9082dd8940ff9a20868f9918e010 7eb737f36dde4acaace827b80bb0a195 18336 "InstallationFolder=C:\Program Files (x86)\Warhorse Studios\KCD_Beta"'
[39E4:3B4C][2016-07-23T08:58:06]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\nb\AppData\Local\Temp\4c1ca9a81e1f40ab868924ea5ce40efc\9654523926e1430b84bd8e2c415e07ee.tmp'
[39E4:3B4C][2016-07-23T08:58:06]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\nb\AppData\Local\Temp\4c1ca9a81e1f40ab868924ea5ce40efc\'
[39E4:3B4C][2016-07-23T08:58:07]i000: Drive for volume F:\ is not suitable (2), skipping.
[39E4:3B4C][2016-07-23T08:58:07]i000: Drive for volume E:\ is not suitable (2), skipping.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to create temporary directory on drive with most free space.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to calculate working folder for large data to ensure it exists.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to create working folder for large data.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to initialize core.
[39E4:3B4C][2016-07-23T08:58:07]i000: Drive for volume F:\ is not suitable (2), skipping.
[39E4:3B4C][2016-07-23T08:58:07]i000: Drive for volume E:\ is not suitable (2), skipping.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to create temporary directory on drive with most free space.
[39E4:3B4C][2016-07-23T08:58:07]e000: Error 0x80070002: Failed to calculate the working folder for large data to remove it.

Why is it trying to use anything other than temp and C: ? please don't do that. I have other drives, but I do not want the installer to use anything other than C: (ie my SSD). Perhaps strangely, E: and F: are not valid drives on my system (J: and K: are), although IIRC this is where USB drives get mounted.

msinfo.txt Magnifier (529 KB) Backer ascl, 08/09/2016 08:06 AM

History

#1 Updated by Backer ascl over 2 years ago

Oops, forgot to say, this error happens immediately. The progress meter is empty.

#2 Updated by Backer ascl over 2 years ago

The log is strange. Using ProcMon, I do not see it failing to create a folder. It seems to successfully create a folder in temp, and a file inside that folder called <random string>.tmp, and successfully write to it.

Anyway, for now, I give up. Let me know if you need more info.

FWIW I am running Windows 10, and have plenty of space on C: (300+ GB).

#3 Updated by ProkyBrambora (QA Team) over 2 years ago

  • Assignee set to Miroslav Louma

#4 Updated by Miroslav Louma over 2 years ago

  • Status changed from New to Investigating

Why is it trying to use anything other than temp and C: ? please don't do that. I have other drives, but I do not want the installer to use anything other than C: (ie my SSD). Perhaps strangely, E: and F: are not valid drives on my system (J: and K: are), although IIRC this is where USB drives get mounted.

This is actually intentional. There have been many complaints about launcher downloading and installing from system drive (usually C), when there are other with much more free space available. This happens, if person buys rather small SSD drive (less than 128/120GiB).

This crash of installation subsystem, you are experiencing, occurs in a routine, which tries to find drive that has most free space available. In your case, the system drive has enough free space to hold installation data and even installed game at the same time. However, since this routine is called during initialization of the installation subsystem, it does not have information about how much data has to be downloaded. That is why, you will get Setup_<number>_failed.txt instead of usual KCD_Beta_Access log files, if an error occurs during this phase.

Essentially, this issue boils down to tweaking this routine and fixing a bug, which occurs on your system (with that specific configuration of storage devices). What would help us do so, is diagnostic information about your storage devices. Could you please upload file with this information here? Instructions can be found here:

https://support.kingdomcomerpg.com/issues/11#note-2

#5 Updated by Backer ascl over 2 years ago

Thanks for the update. I am currently traveling and unable to provide the info, but will do so when I return (2 weeks).

#6 Updated by Backer ascl over 2 years ago

As requested, msinfo output. As you can see, none of my drives have less than 300 GB free.

Happily the latest installer seems to be working.

#7 Updated by Miroslav Louma over 2 years ago

  • Status changed from Investigating to Resolved

Happily the latest installer seems to be working.

This seems strange. Although we did an update to installation subsystem last Tuesday, it was unrelated to this problem.

Nevertheless we are glad that the launcher was able to install the game for you.

Despite this, we have identified and fixed small issues within the routine for finding suitable drive (see above) for downloading installation data, that could occur in specific system configuration such as yours.

If anybody else experiences similar issue, please do not hesitate to create new issue with relevant information (log and MSInfo files).

Also available in: Atom PDF