This article provides easy ways to optimize Microsoft Windows to run the DitStorm Cypher™ using Google Chrome browser.
Turn off Automatically Detect Settings
Turning off the "Automatically detect settings" option in Windows is a classic, highly effective troubleshooting trick for local hardware interfaces (like the DitStorm Cypher).
When this setting is enabled, Windows constantly scans your network in the background using Web Proxy Auto-Discovery (WPAD) to see if a proxy server is required. This background scanning can cause intermittent lag spikes, packet drops, or temporary "hanging" when your laptop tries to communicate with a locally hosted server via your browser.
Here is exactly how to find and disable it to streamline your connection:
For Windows 11
- Open the Start Menu and click on Settings (the gear icon).
- On the left sidebar, click on Network & internet.
- Scroll down on the right side and click on Proxy.
- Under the Automatic proxy setup section, find Automatically detect settings and toggle the switch to Off.
For Windows 10
- Open the Start Menu and click on Settings.
- Click on Network & Internet.
- On the left-hand menu, click on Proxy (near the bottom).
- Under Automatic proxy setup, toggle Automatically detect settings to Off.
What this does for you:
By turning this off, you stop Windows from second-guessing your local network traffic. Your laptop will instantly route data packets straight to your local interface without running a background check first, cutting down on micro-latencies.
Raising Cypher Processing Priority
Because the DitStorm™ Cypher™ relies on a distributed processing model—teaming up its own internal hardware with your laptop's multi-core processor via a web interface (typically running in Google Chrome)—ensuring it gets maximum processing priority comes down to optimizing your operating system and browser settings.
Here is how you can allocate high-priority resources to it on a Windows laptop:
1. Raise Process Priority in Windows Task Manager
Since the DitStorm GUI runs inside a browser window, you can manually elevate the priority of that specific process so Windows feeds it CPU cycles first.
- Open your DitStorm interface in Chrome.
- Press Ctrl + Shift + Esc to open Task Manager.
- Go to the Details tab on the left sidebar (the icon looks like a list with checkmarks).
- Look for chrome.exe. (You will see multiple instances. To find the exact one, you can sort by Memory or CPU while the decoder is running to see which one spikes).
- Right-click the active chrome.exe process, hover over Set priority, and change it from Normal to Above Normal or High.
Note: Avoid choosing Realtime, as this can starve core operating system functions (like your mouse and keyboard drivers) of resources and cause freezing.
2. Prevent Chrome from Sleeping the DitStorm Tab
Google Chrome uses memory and energy-saving features that automatically throttle background or open tabs if it thinks they are inactive. You want to exempt your DitStorm local server address from this.
- Open Chrome and click the three dots in the top-right corner, then select Settings.
- Click on Performance in the left-hand menu.
- Under the Memory Saver section, look for Always keep these sites active.
- Click Add and enter the local IP address or URL you use to access your DitStorm GUI (e.g., the specific local address provided in your setup manual).
- Click Add to confirm. This ensures Chrome never slows down or freezes the decoding engine thread.
3. Adjust Windows Power Options for Maximum Performance
Laptops frequently throttle processing power to conserve battery. You want to force your laptop to run wide open when operating.
- Press the Windows Key, type Control Panel, and hit enter.
- Go to Power Options.
- Select the High Performance or Best Performance plan.
- If you are on Windows 11, you can also do this by going to Settings > System > Power & battery and changing the Power mode dropdown to Best performance.
- Keep your laptop plugged into wall power while operating to prevent the hardware from entering any low-power state that could induce decoding lag.