HookshotBuilder incorrectly requests .NET Desktop Runtime Fresh download of the official v2.1.0 HookshotBuilder.exe displays: "You must install .NET Desktop Runtime to run this application." The dialog reports: #2423
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#2423
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Builder version
v2.1.0
How you built
Hookshot Builder app (Windows)
Game files given to it
A .nup
The error
Visual Studio or Build Tools version, and Windows SDK version
No response
Operating system and free space on the output drive
Windows 11 24h2, 210 gb free
Before you send it
I checked the official v2.1.0 setup list and its .NET archive. The listed archive is 64,088,397 bytes, matches its published SHA-256 (
99a5320f3eaf4e45f5bde2351e1aa0a041f9c730a5b93dea59103fdd7b53427c), and containscoreclr.dll,hostfxr.dll,hostpolicy.dll,System.Private.CoreLib.dllandPresentationFramework.dllunderHookshotBuilder/.That rules out those files being absent from the published runtime archive; it does not establish why they are missing from your installation. The setup's existing-install check currently accepts
installed.txtplus the Builder executable without checking the runtime files.Was this the first installation, or an update/launch of a previously installed copy? Does
installed.txtexist beside that version'sHookshotBuilderfolder? No personal paths or full directory listing are needed. Those two details would help distinguish a skipped incomplete installation from a download/extraction problem.Thanks for the report. Reports of the same problem are now collected in #2505, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2505 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.