SaaS Metrics
Product Positioning & Context
AI Executive Synthesis
User choice, simplified deployment for specific use cases (e.g., USB drives, restricted environments).
This feature request for portable app installation support addresses a clear user preference for flexible deployment options on Windows. Relying solely on MSI installers limits usability for users who prefer portable applications for reasons like no-admin installation, USB drive deployment, or avoiding system-wide changes. Implementing this would enhance the Craft Launcher's versatility and appeal to a broader user segment, including developers and users in restricted environments. Offering both MSI and portable options improves user choice and reduces friction, positioning the launcher as a more adaptable solution.
The Craft App Launcher
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is storytold/craft-launcher?
storytold/craft-launcher is analyzed by our AI as: User choice, simplified deployment for specific use cases (e.g., USB drives, restricted environments).. It focuses on This feature request for portable app installation support addresses a clear user preference for flexible deployment options on Windows. Relying so...
Where did storytold/craft-launcher originate?
Data for storytold/craft-launcher was aggregated directly from the GitHub Open Source community ecosystem, representing raw developer and early-adopter sentiment.
When was storytold/craft-launcher publicly launched?
The initial public indexing or launch date for storytold/craft-launcher within our tracked developer communities was recorded on October 9, 2026.
How popular is storytold/craft-launcher?
storytold/craft-launcher has achieved measurable traction, logging over 2,953 traction score and facilitating 995 recorded discussions or engagements.
Are there active development issues for storytold/craft-launcher?
Yes, we are currently tracking open architectural debates and bug reports for this project on GitHub. There are currently 5 active high-priority issues logged recently.
What are some commercial alternatives to storytold/craft-launcher?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Scribble Party, which offers overlapping value propositions.
How does the creator describe storytold/craft-launcher?
The original author or development team describes the product as follows: "The Craft App Launcher"
Active Developer Issues (GitHub)
Logged: Oct 13, 2026
Logged: Oct 12, 2026
Logged: Oct 11, 2026
Logged: Oct 11, 2026
Logged: Oct 11, 2026
Community Voice & Feedback
Not only the laucnher fails to execute., but pdfcraft also display the same error. I assume it's the same as in all artcraft's apps.
Btw, I updated to the latest version.
Btw, I updated to the latest version.
> 3\. Same issue with the .msi install version?
Same and same. I tried launcher's latest version.
**Portable version:**
Faulting application name: artcraft-launcher.exe, version: 0.3.2.0, time stamp: 0x6acbfd76
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: 0x6a90a9f8
Exception code: 0xc0000409
Fault offset: 0x0000000001941cdd
Faulting process id: 0x74D4
Faulting application start time: 0x1DD59CEBC60A788
Faulting application path: C:\Users\User\Downloads\ABDM\Compressed\artcraft-launcher-0.3.2-windows-x64-portable\artcraft-launcher.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0203731.inf_amd64_05ec0aa74f68ef13\B026470\amdxc64.dll
Report Id: 96674229-084b-4ced-bfdc-b8a6b0db7991
Faulting package full name:
Faulting package-relative application ID:
**.msi version:**
Faulting application name: artcraft-launcher.exe, version: 0.3.2.0, time stamp: 0x6acbfd76
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: ...
Same and same. I tried launcher's latest version.
**Portable version:**
Faulting application name: artcraft-launcher.exe, version: 0.3.2.0, time stamp: 0x6acbfd76
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: 0x6a90a9f8
Exception code: 0xc0000409
Fault offset: 0x0000000001941cdd
Faulting process id: 0x74D4
Faulting application start time: 0x1DD59CEBC60A788
Faulting application path: C:\Users\User\Downloads\ABDM\Compressed\artcraft-launcher-0.3.2-windows-x64-portable\artcraft-launcher.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0203731.inf_amd64_05ec0aa74f68ef13\B026470\amdxc64.dll
Report Id: 96674229-084b-4ced-bfdc-b8a6b0db7991
Faulting package full name:
Faulting package-relative application ID:
**.msi version:**
Faulting application name: artcraft-launcher.exe, version: 0.3.2.0, time stamp: 0x6acbfd76
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: ...
Same issue with the .msi install version?
> 1. Check what the Event Viewer says in the Windows Log/Application section after a failed launch.
> If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for me.
I have the latest update from AMD Adrenaline 26.9.1
Here's the log:
Faulting application name: artcraft-launcher.exe, version: 0.2.1.0, time stamp: 0x6acb8f39
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: 0x6a90a9f8
Exception code: 0xc0000409
Fault offset: 0x0000000001941cdd
Faulting process id: 0x12CC
Faulting application start time: 0x1DD59C29CC85542
Faulting application path: C:\Users\User\Downloads\ABDM\Compressed\artcraft-launcher-0.2.1-windows-x64-portable\artcraft-launcher.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0203731.inf_amd64_05ec0aa74f68ef13\B026470\amdxc64.dll
Report Id: 1f1b9abc-446d-440f-94ae-d5372e20e8be
Faulting package full name:
Faulting package-relative application ID:
> If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for me.
I have the latest update from AMD Adrenaline 26.9.1
Here's the log:
Faulting application name: artcraft-launcher.exe, version: 0.2.1.0, time stamp: 0x6acb8f39
Faulting module name: amdxc64.dll, version: 32.0.31041.3013, time stamp: 0x6a90a9f8
Exception code: 0xc0000409
Fault offset: 0x0000000001941cdd
Faulting process id: 0x12CC
Faulting application start time: 0x1DD59C29CC85542
Faulting application path: C:\Users\User\Downloads\ABDM\Compressed\artcraft-launcher-0.2.1-windows-x64-portable\artcraft-launcher.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0203731.inf_amd64_05ec0aa74f68ef13\B026470\amdxc64.dll
Report Id: 1f1b9abc-446d-440f-94ae-d5372e20e8be
Faulting package full name:
Faulting package-relative application ID:
Check what the Event Viewer says in the Windows Log/Application section after a failed launch.
If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for me.
If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for me.
> Most companies do not have access to the Store.
- I think that for enterprise Windows deployment scenarios—specifically because `.msixbundle` packages cannot be installed on Windows Server Core—Microsoft is currently addressing the issue via https://github.com/PowerShell/PowerShell/issues/27610 . 😄
- Publishing to the Microsoft Store offers the benefit of Microsoft CDN acceleration for downloading the installation package, which simplifies the download process in China. In contrast, if we publish only to winget, the package is downloaded via `github.com`, which tends to be slow in the region.
- I think that for enterprise Windows deployment scenarios—specifically because `.msixbundle` packages cannot be installed on Windows Server Core—Microsoft is currently addressing the issue via https://github.com/PowerShell/PowerShell/issues/27610 . 😄
- Publishing to the Microsoft Store offers the benefit of Microsoft CDN acceleration for downloading the installation package, which simplifies the download process in China. In contrast, if we publish only to winget, the package is downloaded via `github.com`, which tends to be slow in the region.
Most companies do not have access to the Store.
> Its too early for that, mabye in a few months
I can understand if the project currently doesn't intend to sign the MSIX bundle installer. I’ve opened issue #114 at https://github.com/storytold/craft-launcher/issues/114; that issue doesn't require building new artifacts.
I can understand if the project currently doesn't intend to sign the MSIX bundle installer. I’ve opened issue #114 at https://github.com/storytold/craft-launcher/issues/114; that issue doesn't require building new artifacts.
Its too early for that, mabye in a few months
Okay, so I found it.
For me, at least, it's a driver issue.
If you are using an intel integrated graphics card, the driver `igvk64.dll` is probably outdated. You can check this by trying to launch the launcher, then after it exit, run Windows + R, type `eventvwr.msc`, go to Windows apps, and there should be a complete log of errors. Click on the latest one, and it should show what went wrong. A simple driver updated fixed both the launcher and the FilmCraft not launching problem.
For me, at least, it's a driver issue.
If you are using an intel integrated graphics card, the driver `igvk64.dll` is probably outdated. You can check this by trying to launch the launcher, then after it exit, run Windows + R, type `eventvwr.msc`, go to Windows apps, and there should be a complete log of errors. Click on the latest one, and it should show what went wrong. A simple driver updated fixed both the launcher and the FilmCraft not launching problem.
yes windows portable version need ability to download and update portable versions
yeah, windows lacks this option, could be useful with a "destination foler" setting too.
And a auto update checkbox as well
And a auto update checkbox as well
Adding my stone here. Launcher doesn't start either after using .msi install or the portable version.
Windows 10 64x.
Windows 10 64x.
Update: seems like it opens sometimes; samething happens with FilmCraft.
Found it: Failed application name: artcraft-launcher.exe, version: 0.1.3.0, timestamp: 0x6aca57f4
Failed module name: igvk64.dll, version: 30.0.101.
That's the exact same thing happening with filmcraft.
Found it: Failed application name: artcraft-launcher.exe, version: 0.1.3.0, timestamp: 0x6aca57f4
Failed module name: igvk64.dll, version: 30.0.101.
That's the exact same thing happening with filmcraft.
It just randomly opened now, wtf?
Discovery Source
GitHub Open Source Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.