BMM MINER LAUNCHER - DOWNLOAD AND ANTIVIRUS HELP
================================================

QUICK LINK

If mining will not start, read IF-MINER-WONT-START.txt first. It includes a
shorter step-by-step guide and MINER-WONT-START-EXAMPLE.svg as a visual aid.

WHY A WARNING CAN APPEAR

BMM Miner Launcher is an unsigned Early Access release. It configures cryptocurrency
mining and can download and start official mining engines after the user
chooses a coin and clicks Start or Install. Browser and antivirus products
often treat those behaviours as high risk. Microsoft also classifies some
legitimate coin-mining tools as potentially unwanted applications (PUA).

The BMM release contains one launcher EXE. Normal use opens the BMM app without
a second black console. RUN-WITH-DIAGNOSTICS.cmd starts that same EXE from a
diagnostic window, shows the saved startup log after exit and then pauses. The
release does not contain XMRig,
SRBMiner-MULTI, MO-Miner or BzMiner. Those engines
are downloaded later from their official project releases and verified by the
launcher. A warning is still important and should be reviewed rather than
ignored automatically.

BEFORE RESTORING OR RUNNING A DOWNLOAD

1. Download BMM only from the official BearMarketMining download page.
2. Confirm that the filename and version match the page you selected.
3. Compare the ZIP SHA-256 with the value published beside that download:

   Get-FileHash ".\BMM-Miner-Launcher-VERSION.zip" -Algorithm SHA256

4. After extracting the full ZIP, compare the EXE with SHA256SUMS.txt:

   Get-FileHash ".\BMM-Miner-Launcher-windows-x64.exe" -Algorithm SHA256

5. Read START_HERE.txt, SECURITY.md, PRIVACY.md and THIRD_PARTY_NOTICES.md.

IF THE EXACT VERIFIED FILE IS QUARANTINED

Review the exact detection and affected filename in Protection history. If the
detection is VulnerableDriver:WinNT/Winring0 for WinRing0x64.sys or WinRing0.sys,
first confirm that the path is inside BMM's SRBMiner folder and BMM reported
that the official archive passed integrity verification. Select Actions >
Restore. Defender may create a new "Threat found - action needed" entry; open
it and select Actions > Allow on device. Return to BMM and press Start again.

Microsoft identifies this as a valid vulnerable-driver detection associated
with CVE-2020-14979. This SRBMiner build does not start reliably without the
driver, so allowing it is an informed user choice. BMM never changes Defender
settings automatically and does not describe the driver as harmless.

Microsoft's Protection History guide confirms the Restore, then Allow on device
sequence:
https://support.microsoft.com/en-us/windows/security/windows-security/protection-history-in-the-windows-security-app

For any different warning, only consider restoring or allowing the individual
file if you deliberately selected that engine, BMM reports that the official
archive passed integrity verification, and every affected-file detail matches.

Do not disable Defender, Safe Browsing, or another antivirus product. Do not
create broad folder exclusions. If the filename, hash, source, or detection
does not match what you expected, delete the file and report the details.

IF ALLOW ON DEVICE DOES NOT PERSIST

After restoring the exact file, open Windows Security > Virus & threat
protection > Manage settings > Exclusions > Add or remove exclusions. Select
Add an exclusion > File and choose only the exact affected file named in
Protection history inside the verified engine version folder. For the known
WinRing0 detection, this is WinRing0x64.sys or WinRing0.sys. If Protection
history instead names the official miner .exe, select only that exact engine
.exe. Do not choose Folder, File type or Process. Do not exclude the BMM
launcher EXE unless it is the exact flagged release file and its SHA-256 matches
SHA256SUMS.txt. Remove the exclusion when you stop using that engine.

An individual file exclusion reduces protection because Defender no longer
checks that file. Use it only when the filename, path and verified official
archive all match.
BMM never creates an exclusion automatically.

Microsoft's file-exclusion instructions:
https://support.microsoft.com/en-us/windows/security/threat-malware-protection/virus-and-threat-protection-in-the-windows-security-app

ENGINE DOWNLOADS

Every mining start automatically checks the selected engine's official release.
The first start or a verified update can trigger a second warning for that
engine. The button in the engine card is only an optional manual check; users do
not need to press it before Start mining. BMM app updates remain manual during
the unsigned Early Access release.
The launcher displays the official engine project, its license or terms, and
its disclosed developer fee. XMRig is downloaded from the official XMRig
GitHub release. SRBMiner-MULTI is downloaded from its official GitHub release.
MO-Miner is downloaded from its official GitHub release only when an
experimental route or Advanced-mode alternative is selected. Its Windows archive can
exceed 500 MB. BMM verifies the GitHub-published SHA-256 and does not run the
optional MO-Miner administrator installer automatically.
BzMiner is downloaded only for the experimental Warthog CPU + GPU route. BMM
pins reviewed public-beta release v100.04b1 and verifies the official published
SHA-256 before extraction. BMM does not bundle or rehost BzMiner.
IF PEARL, ETC, OR ANOTHER SRBMINER COIN STOPS WHILE INSTALLING

If the launcher reports that Windows blocked a verified mining-engine file
during extraction, the coin and pool have not started yet. Open Windows
Security > Virus & threat protection > Protection history and inspect the exact
detection. For the expected verified SRBMiner WinRing0 file, use Restore, then
Allow on device. For a different expected engine file, make an individual
decision only after verifying all details, then return to BMM and click Start
again.

Do not disable antivirus and do not create a broad folder exclusion. If the
source, filename, integrity result or detection is unexpected, leave the file
blocked and report it. Pearl, Ethereum Classic and the other SRBMiner GPU routes
use the same engine, so the same blocked extraction can affect all of them.

HARDWARE SAFETY

Mining places sustained load on computer hardware and increases heat, fan use
and electricity consumption. Incorrect clock, voltage, power, cooling or
cabling settings can cause instability, data loss, shortened component life or
permanent hardware damage and may affect warranty coverage. BMM does not
automatically change clocks, voltage, power limits or fan curves. Monitor
temperatures and stop if you notice abnormal heat, noise, smell or instability.

Code signing improves identity and reputation but cannot guarantee that a
mining launcher will never be classified as PUA. This Early Access release is
unsigned.
