Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Streamer.bot won't run on a fresh bottle. (mscore.dll not found)

Open
#445 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
tooling

Research direction

Start with the Streamer.bot installation script and the setup described in the issue: a Soda 9.0 runner with a Custom template. Compare fresh-bottle behavior with the Application and Gaming templates, and review the referenced dependencies issue. Done means the documented fresh-bottle setup launches Streamer.bot without the reported mscoree.dll error.

Written by the indexing model from the issue text.

Description

Hi, I'm the uploader of the Streamer.Bot installation script.

Since 18/01 I have been seing users not being able to run the streamer.bot. Everytime the error is related to mscore.dll (both on Bottles support discord channel and on the Streamer.bot linux channel).

The most common error shown is:

0154:err:module:fixup_imports_ilonly mscoree.dll not found, IL-only binary L"Streamer.bot.exe" cannot be loaded 
0154:err:module:loader_init Importing dlls for L"C:\\users\\Public\\streamerbot\\Streamer.bot.exe" failed, status c00000135

This problem is similar to one that I already had when running the script on an "Application" or "Gaming" template, because those install mono (which Streamer.bot requires to not be present at all), so the installation guide explicitly says that bottles should be created using Soda 9.0 runner on a "Custom" template.

Now this error is present even using this workaround.

Might be related to https://github.com/bottlesdevs/dependencies/issues/310?

Dominant language
No language data
Stars
111
Forks
93
Avg merge
1d 1h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bottlesdevs/programs

All issues in bottlesdevs/programs

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.