Troubleshooting Centre

Why it happens

Your browser won't store the login cookie for gsbpro.com, so every page forgets you. Usually it's a site setting in Chrome or Edge (the address bar may say On-device site data not allowed), Safari's Block all cookies, Firefox's strict tracking protection, a privacy extension or adware. An Incognito or private window copies the block from your normal profile, so it won't help.

How to fix it

1. Chrome / Edge: click the icon just left of gsbpro.com in the address bar. If it says On-device site data not allowed, choose Allow site to save data, then Done.
2. Otherwise open Site settings from that icon and set Cookies and site data (or On-device site data) to Allow. Also check Settings > Privacy and security > Third-party cookies and remove gsbpro.com from any "not allowed" list.
3. Safari: Settings > Privacy, untick Block all cookies. Firefox: click the shield left of the address and turn off Enhanced Tracking Protection for this site.
4. Reload the page and log in again in a normal window (not Incognito).
5. Still looping? Try another browser to confirm it's a browser setting, then see the adware entry below.

Why it happens

A typo, a different email from the one you signed up with, Caps Lock, or you're using your Trademaid forum username and password. The forum login doesn't work on gsbpro.com.

How to fix it

1. Check you typed your email address, not a forum username.
2. Retype the password and check Caps Lock (the eye icon shows what you typed).
3. Still failing? Click Forgot password? on the login page and choose a new one.
4. Never made a gsbpro.com account? Sign up free at Get Started.

Why it happens

There is already an account for that email. You may have signed up before, or an earlier attempt did create the account even though it then showed a warning.

How to fix it

1. Click Log in now and log in with that email.
2. Don't know the password? On the login page click Forgot password? and follow the email.

Why it happens

A required field is empty or too short. You only need a first name, an email address and a password of at least 8 characters; last name and platform are optional. You may also see "Please enter your first name", "Please enter a valid email address" or "Your password needs at least 8 characters."

How to fix it

1. Fill in First name.
2. Check the email for typos: one @ and a full domain such as gmail.com.
3. Use a password of 8 or more characters.
4. Click Create my account again.

Why it happens

A temporary problem on our side while saving the account.

How to fix it

1. Wait a minute and try again.
2. If the retry says you already have an account, the first attempt worked: log in instead.
3. If it keeps failing, tell us through the contact form.

Why it happens

gsbpro.com doesn't verify email addresses any more. Signing up logs you straight in. Old "Verify your email" links now just open the login page, and if you never finished the old verification, no account was made.

How to fix it

1. Try logging in with your email and password.
2. If it says they don't match, sign up again at Get Started with the same email. It takes a minute and there's nothing to confirm.
3. If sign-up says you already have an account, use Forgot password?.

Why it happens

Google sign-in is switched off on gsbpro.com. An old bookmarked Google sign-in link shows this message.

How to fix it

1. Log in with your email and password instead.
2. Made your account with Google and have no password? Click Forgot password?, enter the same Gmail address, and set one from the email.

Why it happens

Logins last 30 days in the same browser. Logging out, clearing browser data, or using another browser or device also means logging in again. Your progress is saved on your account, so it comes back when you log in.

How to fix it

1. Log in again. You're taken back to the page you were on.
2. If it happens every few minutes rather than every few weeks, your browser is blocking the login cookie: see I log in but get sent straight back to the login page.

Why it happens

The site's main address is gsbpro.com. The www address was only added recently, so for a while some networks and browsers may still not find it and show "can't be reached", "Server not found" or DNS_PROBE_FINISHED_NXDOMAIN.

How to fix it

1. Type gsbpro.com without the www.
2. Update any bookmark that starts with www.

Why it happens

gsbpro.com won't show inside another site's or app's preview window, and browsers drop the login cookie inside such frames. A development preview is also a different address with its own login.

How to fix it

1. Open a normal browser tab (Chrome, Edge, Firefox or Safari).
2. Type https://gsbpro.com in the address bar yourself.
3. Log in there.

Why it happens

An adware extension or "search" program can change browser settings, open pop-ups, redirect pages and block site data. Signs: your search engine keeps changing, odd new tabs appear.

How to fix it

1. Chrome: Settings > Extensions, and remove anything you don't recognise.
2. Chrome: Settings > Reset settings > Restore settings to their original defaults.
3. Windows: Settings > Apps, and uninstall unknown programs added recently (search bars, "PDF" or "converter" tools).
4. Run a full scan with Windows Security or the free Malwarebytes.
5. Allow gsbpro.com to save data again and log in.

Why it happens

GSB Pro emails come from noreply@updates.gsbpro.com and often land in Spam, Junk or Promotions. A typo in your email address, or a strict work filter, also stops them.

How to fix it

1. Search every folder for updates.gsbpro.com or "GSB Pro".
2. Mark it Not spam and add noreply@updates.gsbpro.com to your contacts or safe senders.
3. Check the email shown on your Account page is right.
4. Nothing after 10 minutes? Tell us through the contact form.
5. Licence and registration emails come from Trademaid, not GSB Pro.

Why it happens

You can't change your email or name yourself on gsbpro.com yet.

How to fix it

1. Send a request through the contact form, ideally from your old address.
2. Give both the old and new email addresses (or the name to use).
3. This only changes gsbpro.com. Your Trademaid forum and licence emails are separate records.

Why it happens

There's no delete button on gsbpro.com. Marketing emails are opt-in.

How to fix it

1. To stop emails, use the unsubscribe link in the email, or ask us.
2. To delete your account, send a request through the contact form from the account's email address.

Why it happens

There are two separate logins, run by two different parties. gsbpro.com uses your email address and the password you chose here (for the training and members area). The Trademaid forum uses a username and the password Trademaid emailed you (for the trial download, the forum and buyers' files). Neither works on the other site.

How to fix it

1. On gsbpro.com, log in with your email and gsbpro.com password. Reset it with Forgot password.
2. On the Trademaid forum, log in with your forum username and the emailed password. Reset it on the forum's Recover Lost Password page.
3. You can use the same email for both, but they stay separate accounts.

Why it happens

For privacy, the site shows this message whether or not the email has an account. No email usually means a different address from the one you signed up with, or a spam filter.

How to fix it

1. Wait up to 10 minutes, then check Spam, Junk and Promotions for "Reset your GSB Pro password" from noreply@updates.gsbpro.com.
2. Check you used the email you signed up to gsbpro.com with (not one you only use on the forum).
3. Ask for the link once more.
4. Still nothing? Use the contact form.

Why it happens

gsbpro.com reset links last 1 hour and work only once.

How to fix it

1. Click Ask for a new link.
2. Open the newest email and use it within the hour.

Why it happens

The link was cut short, usually by copying only part of it or by the email program wrapping it.

How to fix it

1. Click the button or link in the email rather than copying it.
2. If that fails, ask for a new link.

Why it happens

Sign-up and Forgot password need at least 8 characters. Changing your password on the Security page is stricter: it needs an upper-case letter, a lower-case letter, a number and a symbol, and the button stays grey until every tick is green.

How to fix it

1. On the reset page, use 8 or more characters.
2. On the Security page, include A-Z, a-z, 0-9 and a symbol such as ! @ # $ % ^ & * (spaces and some symbols aren't counted), and type it identically in Confirm Password.
3. Easier option: log out and use Forgot password?, which only needs 8 characters.

Why it happens

Google sign-in is switched off, and accounts made with Google never had a password.

How to fix it

1. On the login page click Forgot password?.
2. Enter the same Gmail address you used with Google.
3. Open "Reset your GSB Pro password" and choose a password. You're logged in straight away.
4. From then on, log in with your email and that password. Your progress is kept.

Why it happens

The forum's Recover Lost Password page needs both your forum username and the email on the account, and both must match. It then emails you a new password.

How to fix it

1. On the forum login page click Forgot password?, or open Recover Lost Password.
2. Enter your Username and E-Mail exactly as registered, then click Submit.
3. Check your inbox (and spam) for the new password from Trademaid, then log in.
4. Change it to one you'll remember in the forum's control panel (see below).
5. Don't know your username? See I forgot my Trademaid forum username.

Why it happens

The forum has no way to look up a username, and resetting the password needs it.

How to fix it

1. Search your email for the original Trademaid welcome email (subject starting "[GSB Forums]"). It shows your username.
2. If you can't find it, email Peter at peterzwag@gmail.com with the email address you registered with.
3. Don't register a second account: extra accounts can look like trial abuse.

Why it happens

Forum usernames can't contain any of these characters: [ ] ' < > \ | " , @. So you can't use your email address as the username. A name someone else already has is also rejected.

How to fix it

1. Choose a plain username such as JohnSmith, with no @, comma, quotes or brackets.
2. Put your email address in the E-Mail box instead. There's no confirm box, so check it carefully.
3. If that name is taken, add a number.

Why it happens

Usually a copy-and-paste problem: a space copied before or after the password, or the wrong case. Also check you're typing your forum username, not your email address.

How to fix it

1. Paste the password, then delete any space before or after it, or type it by hand.
2. Use your forum username exactly as registered.
3. Leave Browse the board invisible and Secure Login unticked on your own PC.
4. Still failing? Use Recover Lost Password with your username and email.
5. If that fails too, email Peter at peterzwag@gmail.com with your username.

Why it happens

There's no password box when you register: the forum emails you one. You change it, and your email, in the forum's control panel once you're logged in.

How to fix it

1. Log in to the Trademaid forum.
2. Open the User Control Panel (your profile) and edit your profile.
3. Enter the new password (or email) and save.
4. Can't log in because your old email no longer works? Email Peter at peterzwag@gmail.com.
5. Your licence email (from SoftwareKey) is a separate record; changing the forum email doesn't change it.

Why it happens

The GSB PAID USERS ONLY forum (with the Resource Manager download and buyers' threads) has its own separate password. It isn't your login password. Buyers get access after buying and returning the signed NDA; trial users can't get in.

How to fix it

1. Trial user? This area is for buyers only.
2. Bought GSB? Make sure you've returned the NDA (see After you buy). Turning on access is done by hand, normally within one working day.
3. Still locked out? Email Peter at peterzwag@gmail.com with your forum username and the email you paid with.

Why it happens

The License ID and Activation Password you get after buying are for activating the software, not for logging in to the forum or gsbpro.com. You still log in to the forum with your forum username and password.

How to fix it

1. Use the License ID and Activation Password only when the software asks to be activated.
2. Use your forum username and password on trademaid.info, and your email and password on gsbpro.com.
3. Keep all of these private: never post licence details in the forum. Email them to Trademaid if they're needed.

Why it happens

The members area, Training Hub, Get the Software, Member Bonuses and Account pages need a gsbpro.com login. After logging in you're taken back to the exact page or lesson.

How to fix it

1. Log in, or sign up free if you haven't yet.
2. If you keep coming back to the login page, your browser is blocking the login: see I log in but get sent straight back to the login page.

Why it happens

Saving the tick failed because of a temporary problem, or your login had run out.

How to fix it

1. Click Mark as done again.
2. If you're sent to the login page, log in; you come back to the lesson.
3. If it keeps happening, click Email the team in the chat or use the contact form.

Why it happens

Progress is stored on your gsbpro.com account, not in the browser. You may be logged in with a different email, or the progress didn't load this time.

How to fix it

1. Check which email you're logged in with on the Account page.
2. Reload the page.
3. Still 0%? Tell us through the contact form and say which email you used.

Why it happens

Lessons are YouTube videos. Work or school networks that block YouTube, ad or script blockers, browser extensions and some VPNs (which trigger YouTube's bot check) stop them. Very old browsers can't play them.

How to fix it

1. Turn off your ad blocker for gsbpro.com, or try another browser.
2. Try without the VPN or off the work network (a phone hotspot is a quick test).
3. Check youtube.com plays in a normal tab.
4. Reload the Training Hub.
5. Still stuck? Email the team and say which lesson.

Why it happens

Playing a lesson's video marks it done automatically. Lessons without a video yet show Coming soon; they still have a written guide. An amber Updated advice label means Peter Zwag has changed his advice since the video was made.

How to fix it

1. For a Coming soon lesson, click Read the guide, then Mark as done.
2. For Updated advice, open it and follow the Strategy Guide link: it overrides the video.

Why it happens

Member Bonuses are only for logged-in members. This shows after a temporary error or when your login has run out.

How to fix it

1. Refresh the page.
2. If you're sent to the login page, log in and open Member Bonuses again.
3. Still failing? Try again later or tell the team.

Why it happens

gsbpro.com doesn't host any downloads. The GSB trial and full versions come from the Trademaid forum (with your forum login), and add-ons from Trademaid's pages.

How to fix it

1. Open Get the Software in the members area and follow the steps there.
2. Register on the Trademaid forum if you haven't; the trial link comes by email.
3. Licence questions go to Peter at peterzwag@gmail.com.

Why it happens

Either the question box was empty, or the conversation has grown too long (around 10 questions, or a very long answer) and the chat can't continue it.

How to fix it

1. Want to keep the conversation? Click Email the team first.
2. Open gsbpro.com in a new tab (reloading the same tab keeps the old chat), or close the tab and reopen the site.
3. Ask your question again in the fresh chat.

Why it happens

The chat allows about 40 questions an hour from one internet address. Shared office networks and VPNs share the limit.

How to fix it

1. Wait up to an hour, or click Email the team to reach a person.

Why it happens

The chat is hidden while the assistant is switched off or temporarily unavailable.

How to fix it

1. Use the contact form instead.
2. Check back later; the bubble returns when the assistant is back.

Why it happens

A temporary problem with the AI service or your connection. You may also see "Sorry, I couldn't connect" or "Sorry, I didn't get an answer". The chat is an AI assistant; Email the team reaches a person.

How to fix it

1. Check your internet connection and ask again.
2. If it keeps failing, click Email the team, or use the contact form.

Why it happens

If you're logged out you need to enter an email address so we can reply. Very long conversations can also fail to send, sometimes showing "Please check your email address."

How to fix it

1. Enter a valid email address if asked (logged-in members don't need to).
2. If it still won't send, use the contact form and paste the key part of the conversation.
3. There's no confirmation email; the reply comes from the GSB Pro team by email.

Why it happens

The name needs at least 2 characters, the subject at least 5 and the message at least 20.

How to fix it

1. Fill in every field, with a few words in the subject and a sentence or two in the message.
2. If you see "Your message couldn't be sent", email andrew.gibbs@gsbpro.com directly.
3. A receipt, "GSB Pro - Message Received", is emailed when it goes through. Check spam if you don't see it.

Why it happens

You aren't logged in to the Trademaid forum, or you don't have a forum account yet. Trademaid's forum only shows attachments to logged-in members.

How to fix it

1. Register at trademaid.info/forum (Register, top right) if you haven't already.
2. Log in with your forum username and the password Trademaid emailed you.
3. Check the top bar shows your username instead of Not logged in.
4. Reopen the post (the trial is in the GSB EXE FILE post) and the download links will appear.
5. Still blocked after logging in? Your browser may be refusing cookies. Allow cookies for trademaid.info and log in again.

Why it happens

The forum emails you a generated password, so the account can't be used until that email arrives. It's usually caught by a spam filter, or the email address was mistyped (there's no confirm field). Now and then Trademaid's forum mail server itself stops sending for a while.

How to fix it

1. Wait 10 minutes, then check your spam or junk folder.
2. Search all your mail for trademaid. The sender is info@trademaid.info and the subject is "[GSB Forums] Download FREE 14 days of GSB".
3. Don't register a second account. Extra accounts can look like trial abuse and you may be blocked.
4. Still nothing, or you think you mistyped the address? Email Peter at peterzwag@gmail.com with your forum username and the correct email address. He can fix the account and password by hand.

Why it happens

This misleading message is what the forum shows for a direct file link (files.php?...) when you aren't logged in. It also appears if the file has since been removed, for example an old trial installer that has been replaced.

How to fix it

1. Log in to the forum first, then try the link again.
2. If it still fails, the file is gone. Open the GSB EXE FILE post and download the newest installer from there, rather than using an old bookmark or a link in older help pages.

Why it happens

That's the buyers' section (GSB PAID USERS ONLY), which holds the Resource Manager download, beta mode and other buyer-only threads. It has its own separate password, not your login password. Buyers get it after paying and returning the signed NDA. Trial users can't get in.

How to fix it

1. Don't type your forum login password here. It won't work.
2. If you've bought GSB, complete the NDA on Trademaid's "Things you need to do after purchase" page and send it back.
3. Allow one working day: Peter turns on buyers' access by hand.
4. Bought GSB, sent the NDA and still no buyers' password? Email Peter at peterzwag@gmail.com with your forum username.

Why it happens

Buyers' access is switched on by hand once Peter matches your payment to your forum account and has your signed NDA. If your PayPal email differs from your forum email he may not be able to find you. Your License ID and Activation Password are for activating the software, not for logging in to the forum.

How to fix it

1. Log in to the forum with your normal forum username and password, not your License ID.
2. Check you've filled in and returned the NDA. Without it you won't get the buyers' forum, systems or Resource Manager.
3. Wait one working day after sending the NDA.
4. Then email Peter at peterzwag@gmail.com with your forum username, the email you paid with and the payment date. Mention it if your PayPal email isn't the same as your forum email.

Why it happens

Buyers' forum access, Resource Manager and updates last for one year after purchase, then continue only while your software maintenance is current. You keep using the GSB version you had when maintenance ran out.

How to fix it

1. Renew software maintenance through Trademaid's purchase page.
2. Email Peter at peterzwag@gmail.com with your forum username and renewal details so he can switch access back on.

Why it happens

This is deliberate. Peter locked new threads because of duplicate questions, and because nobody gets notified about a new topic, so it would go unanswered.

How to fix it

1. Post your question in the existing General support questions thread, or in the thread for your product: Resource Manager (tid 208), GSB Automation (tid 266), EWFO (tid 123) or PA Pro (tid 127).
2. Subscribe to that thread (the option is under Quick Reply) so you're emailed when someone answers.

Why it happens

Posts in a new or quiet thread notify nobody. Other users are subscribed to the main threads, so questions there get seen. Peter is in Australia, so replies can come overnight for you.

How to fix it

1. Repost in the General support questions thread ("If in doubt, post here") or your product's thread.
2. Subscribe to the thread under Quick Reply so you see the answer.
3. Include your GSB version (from the title bar), what you did, the exact error and a screenshot.

Why it happens

Trademaid's forum mail server occasionally stops sending, so notifications pause. If you get an email for a post you can't find, Peter has usually deleted a spam post after the notification went out.

How to fix it

1. Check that you're subscribed to the thread (option under Quick Reply).
2. During a mail outage, check the thread by hand for a while.
3. Ignore notifications for posts that have vanished: they were spam.

Why it happens

Forum attachments must be under 1 MB.

How to fix it

1. Zip the file, which often brings it under the limit.
2. For bigger files (price data, logs), share a Dropbox, pCloud or WeTransfer link in your post, or email it to Peter.
3. Never post TeamViewer or AnyDesk IDs and passwords on the forum. Email them to Peter.

Why it happens

Peter normally replies within 24 hours on Australian working days, but emails sometimes land in his spam folder or bounce during Trademaid mail-server changes.

How to fix it

1. Allow 24 hours, not counting Australian weekends.
2. Email peterzwag@gmail.com again, ideally from a different email address.
3. Post a short note in the General support questions thread saying you've emailed him. Don't post licence codes or passwords there.

Why it happens

The trial is attached to the first post of the GSB EXE FILE thread on the Trademaid forum, which only shows downloads to logged-in members. The post holds several older attachments that have expired.

How to fix it

1. Log in to the Trademaid forum.
2. Open the GSB EXE FILE post.
3. Download the newest Online installer (GSBSetup.msi), marked for trial users. Ignore older attachments further down.
4. Run it and install to the default C:\GSB.

Why it happens

A false positive. GSB's files are obfuscated to stop people decompiling them, and heuristic antivirus treats obfuscated code as suspicious. Only a handful of engines on VirusTotal usually flag it.

How to fix it

1. Worried? Check the file at virustotal.com.
2. Whitelist the installer before you run it, and exclude C:\GSB (which covers C:\GSB\Workers and C:\GSB\Cloud Workers).
3. At the end of the install, don't tick Launch GSB. Some antivirus deleted the files when GSB was launched straight from the installer.
4. Whitelist new exes that Resource Manager downloads later, and re-add exclusions after a TradeStation upgrade.
5. Files already deleted? Uninstall, delete C:\GSB, restart, add the exclusions, then reinstall.

Why it happens

GSB needs .NET Framework 4.8 and an up-to-date Windows. A fresh or unpatched Windows (including Windows Server) often lacks one or the other.

How to fix it

1. Run Windows Update until there's nothing left to install, then restart.
2. Install or repair .NET Framework 4.8 from Microsoft.
3. Start GSB again. If the manager won't open, try GSB Standalone first.
4. Still crashing? Post in the forum with the files from C:\GSB\Exceptions, or email Peter.

Why it happens

GSB relies on standard Windows parts such as Performance Counters. Stripped-down Windows builds (made with tools like NTLite) remove them, and GSB crashes at start-up.

How to fix it

1. Use a standard Windows 10 or 11 install with all updates.
2. If you've removed Windows components, put Performance Counters back or reinstall Windows normally.
3. On non-English Windows, make sure you're on a current build (an old 2020 bug stopped GSB running there).

Why it happens

By default GSB's licensing won't run in a virtual machine (Parallels, VMware, Hyper-V, AWS and similar). That includes Mac and Linux users running Windows in a VM.

How to fix it

1. Run GSB on a physical Windows PC, or rent a dedicated (not virtual) server.
2. On an Intel Mac, Boot Camp runs Windows natively and has worked for users.
3. If you really need a VM, ask Peter before you buy. Trademaid's terms say VMs aren't supported unless arranged beforehand, and VPS cores are usually poor value for GSB.

Why it happens

Peter's explanation: this usually appears after an update where a manager or worker was still open, so some files didn't update and the DLL versions no longer match. Remote Desktop sessions can also trigger it.

How to fix it

1. Close every GSB manager, worker and GSB Automation window (or use Kill All in Resource Manager).
2. Run Resource Manager as administrator and let it update again.
3. If it only happens over Remote Desktop, connect with AnyDesk or TeamViewer instead, or start GSB at the PC itself.
4. Still there? Email Peter for a remote session.

Why it happens

Windows display scaling. GSB doesn't scale well above 100% on high-resolution screens.

How to fix it

1. Right-click the GSB exe (or its shortcut) → Properties → Compatibility → Change high DPI settings.
2. Tick Override high DPI scaling behaviour and choose System (Enhanced). Click OK and restart GSB.
3. If that doesn't help, try Windows' compatibility troubleshooter ("program doesn't display correctly"), or set Windows display scaling to 100%.

Why it happens

GSB checks online when it starts. Without an internet connection it can report that your version is too old and close. Managers also need the internet because workers report through Trademaid's servers.

How to fix it

1. Connect to the internet and start GSB again.
2. Check a firewall or antivirus isn't blocking GSB from going online.
3. Travelling? Start GSB while online, then sleep the laptop instead of closing GSB.

Why it happens

Either the trial build you installed is past its built-in expiry date (the trial installer is replaced every few months), or a registration bug in that build gave you a short or zero-day trial. Once a faulty build has run, installing a newer one over it may not fix the expiry on that PC.

How to fix it

1. Check the GSB EXE FILE post for a newer installer. If there is one, install it.
2. Don't keep re-running GSB or reinstalling, and don't register a new forum account or use another machine to get around it.
3. Still expired? Email Peter at peterzwag@gmail.com with your forum username and the build number. He can send a replacement licence file to copy into C:\GSB and C:\GSB\Cloud Workers, or fix it in a remote session.
4. If he sends updated program files instead, see "My trial stopped working part way and won't update itself" for where to copy them.

Why it happens

Each trial build has a hard-coded expiry. Once it has passed, the trial doesn't pull in new files by itself.

How to fix it

1. Download and install the newest installer from the GSB EXE FILE post. Peter refreshes it when old installers expire.
2. If there isn't a newer one yet, ask in the General support questions thread. Peter has posted a zip of updated files for this.
3. Manual fix with that zip: close GSB, unzip the files first, then copy them over the old ones in all three folders: C:\GSB, C:\GSB\Workers and C:\GSB\Cloud Workers.
4. Restart GSB while connected to the internet.

Why it happens

Every GSB build expires after about three months by design, so buggy and incompatible old versions drop out. Occasionally Trademaid forgets to extend a build and everyone is hit on the same day.

How to fix it

1. Check your internet connection and restart GSB.
2. Licensed users: run Resource Manager as administrator and let it download the current build.
3. Trial users: install the newest installer from the GSB EXE FILE post.
4. If everyone is reporting it at once, check the beta builds thread and the General support questions thread. Peter usually posts a fixed build within hours.

Why it happens

GSB writes inside its own folder. Under C:\Program Files Windows blocks those writes, cloud-sync folders (OneDrive, Dropbox, Google Drive) interfere, and a read-only C:\GSB causes failures too.

How to fix it

1. Install to the default C:\GSB.
2. If you moved GSB, set Tools → App Settings → Data (Public Data Directory) to the folder that holds the GSB exes.
3. Clear the read-only flag on C:\GSB (right-click → Properties, or attrib -r C:\GSB /s /d in a command prompt).

Why it happens

The desktop icons start the build named in C:\GSB\version.txt. If that file names a build that isn't there, the shortcut fails.

How to fix it

1. Open C:\GSB and double-click the newest GSBManager.<version>.exe directly.
2. Or edit version.txt so it matches the version of the newest GSBManager exe in that folder.

Why it happens

GSB keeps almost everything in C:\GSB (only registration info goes elsewhere). New builds sit beside old ones with new exe names. But running the trial installer on a licensed PC resets it to trial mode.

How to fix it

1. Back up C:\GSB\Data (Contracts.txt, Price Data.txt, Sessions.txt, and the Price Data and Settings folders) and note your share keys.
2. Trial users: rename or delete C:\GSB, then reinstall from the forum.
3. Licensed users: email Peter first. Don't run the trial installer yourself, or your registration will be reset.

Why it happens

The trial is 14 days on at most two machines per person. Using new machines, VMs or extra accounts to stretch it breaks Trademaid's rules and can get you banned and licences revoked.

How to fix it

1. Email Peter at peterzwag@gmail.com before you buy and explain what you still need to test. He does extend trials when asked.
2. Don't make a new forum account or reinstall on another PC to restart the trial.

Why it happens

Running the trial online installer (GSBSetup.msi) on a licensed PC resets the registration to trial mode. After you buy, new builds come through Resource Manager, not the forum installer.

How to fix it

1. Don't run the trial installer again.
2. Email Peter at peterzwag@gmail.com with your forum username and purchase details so he can restore your registration.
3. From now on, update GSB through Resource Manager.

Why it happens

Your licence is still activated on an old install or computer, so there are no activations left. Common after reinstalling Windows or moving PCs.

How to fix it

1. If you can, deactivate the old computer in Trademaid's licence portal (see "Moving GSB, EWFO or PA Pro to a new PC").
2. Otherwise, or if the portal shows no deactivations left, email Peter at peterzwag@gmail.com with your forum username and purchase details. He'll deactivate the old activation.
3. Then activate again on this PC.

Why it happens

GSB's licence file, GSB_IPP3.xml, isn't in the folder the exes run from. It's deliberately left out of updates (there are several variations of it), so it goes missing if builds end up in a new folder.

How to fix it

1. Search your old GSB folder for GSB_IPP3.xml.
2. Copy it into the folder that holds the GSB exes (normally C:\GSB), and into any worker folders that run from elsewhere.
3. Can't find it? Email Peter at peterzwag@gmail.com.

Why it happens

Licences are per physical computer but can be moved. For GSB, EWFO and PA Pro you can deactivate the old PC yourself in Trademaid's SoftwareKey licence portal. Resource Manager, GSB Automation and Alertmon can't be moved that way: Peter has to revoke them.

How to fix it

1. Open the SoftwareKey Customer License Portal and log in (see "I can't log in to the SoftwareKey licence portal" if that fails).
2. Open License Details, which shows Activations Left and Deactivations Left, then click Manage Installations.
3. Click the red X next to the old computer to deactivate it.
4. Activate on the new PC. GSB itself: install the trial from the forum first, then activate.
5. If Deactivations Left is zero, or the old PC is dead and not listed, email Peter at peterzwag@gmail.com.
6. For Resource Manager, email Peter its new codes from the new PC (see the Resource Manager entries).
7. Tip: on builds from 67.15, label each machine on the registration screen so you know which one to revoke later.

Why it happens

The portal and Trademaid's help disagree. Trademaid's help says to log in with your License ID and Activation Password. The portal says it accepts a Customer ID, License ID or invoice number, but not activation passwords.

How to fix it

1. Enter your License ID (from your licence email) in Email or Login ID.
2. If your password is refused, click Forgot your password? and search by your License ID or email address.
3. Don't use the New Customers box. It creates a new, empty account.
4. Still stuck? Email Peter at peterzwag@gmail.com for your customer ID and password, or ask him to move the licence for you.

Why it happens

The old activation is still recorded against the PC's previous installation, and the trial files GSB needs aren't there any more.

How to fix it

1. Back up your data and systems first if you still can.
2. Install the trial from the GSB EXE FILE post. Licensed GSB needs the trial files present.
3. Install Resource Manager from the buyers' forum (tid 208).
4. Deactivate the old installation in the licence portal, or email Peter to revoke it, then activate GSB again.
5. Email Peter Resource Manager's new codes as plain text with your purchase or maintenance date.

Why it happens

A GSB licence covers one PC, even if the two PCs never run at the same time. On that one PC you can run as many copies as you like. A second PC needs its own licence.

How to fix it

1. Buy an extra licence from Trademaid (extra-licence discounts are offered on the day you first buy).
2. Or, if you've retired the first PC, deactivate it and activate the new one (see "Moving GSB, EWFO or PA Pro to a new PC").
3. To use workers on another PC without licensing it, run them on the licensed PC and share them through matching share keys.

Why it happens

Paid licences are activated with the License ID and Activation Password Trademaid sends you. If you also own other SoftwareKey-licensed software (such as Adaptrade), a lookup link may send you to that vendor's portal instead.

How to fix it

1. Use the License ID and Activation Password from Trademaid's licence email, not anything from another vendor.
2. If GSB doesn't show the activation window, hold Shift while you start it to bring it up.
3. Can't find your codes? Email Peter at peterzwag@gmail.com. He can resend licence codes for GSB, EWFO and PA Pro.

Why it happens

A licensed PC has been known to ask for activation again under a new Windows user account. Trademaid hasn't published why.

How to fix it

1. Ask Peter before switching Windows accounts on a licensed machine.
2. If it's already happened, don't keep activating (you'll use up activations). Email Peter at peterzwag@gmail.com.

Why it happens

Updates, Resource Manager and buyers' forum access are free for 12 months after purchase, then need paid software maintenance. When maintenance lapses you keep, for good, the version released at your expiry date.

How to fix it

1. Check your maintenance expiry date. Resource Manager shows it.
2. Renew maintenance through Trademaid's purchase page.
3. Email Peter at peterzwag@gmail.com with your renewal so he can register Resource Manager and restore access.

Why it happens

Resource Manager uses DLLs that clash with GSB's. Installed in the same folder as the GSB exes, it breaks both. It also expects the trial GSB to be in C:\GSB already.

How to fix it

1. Keep the trial GSB installed. Resource Manager updates those files; don't uninstall them.
2. Download the newest installer from the first post of the buyers' Resource Manager thread (tid 208).
3. Install it to its own folder, the default C:\GSB\GsbResourceMonitor\, never beside the GSB exes.
4. Always start it with right-click → Run as administrator. Without admin rights it can't update GSB or read CPU temperatures.

Why it happens

Resource Manager is free while your GSB purchase is under a year old or your maintenance is current, but it must be registered. Until then it runs for 30 days in trial mode. Each install shows two codes that Peter turns into a registration code.

How to fix it

1. Start Resource Manager and choose Register on the start-up prompt.
2. Copy both codes as plain text (not a screenshot).
3. Email them to Peter at peterzwag@gmail.com with your purchase or maintenance date.
4. Leave Resource Manager open on that screen until he replies. If you close it, the codes change. You can run a second copy meanwhile.
5. Enter the code he sends back.

Why it happens

Resource Manager was closed or restarted after you copied the codes, so the codes changed. A move to a new Resource Manager version (such as the 64-bit change) can also need new codes.

How to fix it

1. Open Resource Manager and copy the two codes it shows now.
2. Email them again to Peter with your purchase or maintenance date, and say the last code didn't work.
3. Keep Resource Manager open until his reply arrives.

Why it happens

Usually antivirus blocking or deleting a file (a false positive on OpenHardwareMonitorLib, the CPU-temperature library), or an old Resource Manager.

How to fix it

1. Exclude C:\GSB, the Resource Manager folder and your TradeStation folders from antivirus.
2. Install the newest Resource Manager from tid 208. That fixed it for users on old versions.
3. If antivirus already deleted files, reinstall after adding the exclusions.
4. Still nothing? Email Peter.

Why it happens

Resource Manager isn't running as administrator, it's too old (it must be a May 2024 or later build since Trademaid's database move), a manager or GSB Automation window is open and locking files, or the GSBManager folder setting is wrong.

How to fix it

1. Close every manager, worker and GSB Automation window.
2. Start Resource Manager with right-click → Run as administrator.
3. On the Update tab, check updates are on and the GSBManager folder is C:\GSB.
4. If your Resource Manager is older than May 2024 (or more than about six months old), install the newest one from tid 208.
5. Only the workers updated? Copy the new GSBWorker.<version>.exe from C:\GSB\Workers to C:\GSB, rename it GSBManager.<version>.exe, and copy version.txt and gsb.pdb with it.

Why it happens

Trademaid's download server wasn't serving the file at that moment. It's on Trademaid's side, not your PC.

How to fix it

1. Wait a few hours and try again. It usually works on a later attempt.
2. Make sure your Resource Manager is a 2024 or later build.
3. If it keeps failing for a day or more, email Peter for a remote session.

Why it happens

Resource Manager's self-update has had bugs in some versions, so saying Yes to "install the new RM" fails or stops straight away.

How to fix it

1. Close Resource Manager.
2. Install the newest Resource Manager from tid 208 over the old one, or overwrite its files with the ones Peter posts in the Resource Manager threads.
3. Start it again as administrator.

Why it happens

When many users see this at once straight after an update, it's a fault on Trademaid's side, usually fixed within hours.

How to fix it

1. Check the beta builds thread and tid 208 for Peter's notice.
2. Wait a few hours, then restart Resource Manager (as administrator) so it fetches the fix.

Why it happens

Peter: you have a bad mix of new and old DLL files. A manager or worker was open while Resource Manager updated, so some files were locked and didn't update.

How to fix it

1. Close all managers, workers and GSB Automation, or use Kill All in Resource Manager.
2. Run Resource Manager as administrator and let it update again.
3. Or unzip the update files Peter posts and overwrite everything in C:\GSB, C:\GSB\Workers and C:\GSB\Cloud Workers.
4. Still failing? Email Peter with a screenshot. He usually fixes it by email or remote session.

Why it happens

Managers and workers must be on the same build. Major builds can't talk to older ones, so an old manager won't find updated workers. Resource Manager can also update workers in the middle of a test.

How to fix it

1. Update managers and workers together: close the manager, let Resource Manager update, then open the new manager.
2. Check C:\GSB has a GSBManager.<version>.exe matching the worker version.
3. Before a long run, turn off automatic downloads on Resource Manager's Update tab, and turn them back on afterwards.

Why it happens

There's no manager exe of the same build in C:\GSB. Workers only start through a matching manager.

How to fix it

1. Check C:\GSB holds GSBManager.<version>.exe for the same version as the workers, and that version.txt names that version.
2. If it's missing, copy the worker exe across and rename it (see "Resource Manager isn't updating GSB").

Why it happens

The GSBManager folder on Resource Manager's Update tab doesn't point to C:\GSB, or antivirus interfered.

How to fix it

1. On the Update tab, set the GSBManager folder to C:\GSB.
2. Exclude C:\GSB from antivirus.
3. Copy the manager exe into C:\GSB by hand this time.
4. If it keeps happening, turn on Resource Manager logging and send Peter the log folder.

Why it happens

Resource Manager reads the version from the worker's file name. A worker called plain GSBWorker.exe won't update.

How to fix it

1. Rename the worker so it includes its version, e.g. GSBWorker.68.92.exe.
2. Check the paths under WorkerAllocation → WorkerItemGroups and on the Update tab match your install.

Why it happens

Resource Manager's configuration is missing or doesn't match this machine. Configs are saved per machine (config.<machine name>), so reinstalling doesn't help.

How to fix it

1. In Resource Manager press Load and choose the default config in its config subfolder that matches your PC's RAM.
2. Adjust the worker groups and save.
3. Before upgrading Resource Manager in future, use Save As to back up your config.

Why it happens

Managers and workers find each other by share key (workplace user and password). They must be identical on every manager and worker. The default key shares with the public GSB cloud. Reset App Settings also resets share keys.

How to fix it

1. In the manager, open Tools → App Settings → Workplace, remove the default gsbcloud user and password, and enter your own unique ones.
2. Open a worker from each worker folder and enter the same key, then save.
3. Use Kill All in Resource Manager and let it restart the workers.
4. Keep at least one worker on your own PC. Each PC that runs GSB needs its own licence.
5. Note your keys before resetting App Settings, and check them after updates.

Why it happens

Cloud workers are donated by other users' Resource Managers and Trademaid's servers, so numbers vary. You lose the public cloud if your build is older than the current major release, or if your share key isn't the gsbcloud default.

How to fix it

1. Keep GSB and Resource Manager updated, especially after a major release.
2. Check the manager's workplace is still set to gsbcloud if you want the public cloud.
3. After a Trademaid outage, restart managers and workers.
4. For dependable capacity, run your own workers or hire a server.

Why it happens

Windows 11 gives background programs low CPU priority. Peter's December 2025 note on the Resource Manager thread says the 20251127 installer gives better performance on Windows 11.

How to fix it

1. Install the newest Resource Manager from tid 208 (20251127 or later).
2. On an older Resource Manager, turn on tiled mode for workers (StartWorker Tiled = True), or bring the worker windows to the front.
3. Use Windows Task Manager to check real CPU use, which older Resource Managers misreport.

Why it happens

Since the June 2026 major update, beta mode is switched on by copying Trademaid's mode.txt file into C:\GSB. Old forum posts describing config files or Tools → Impersonate apply to older builds. Beta features are experimental and more likely to be buggy.

How to fix it

1. Download mode.txt from the buyers' beta mode thread (tid 249), or ask Peter for it.
2. Copy it into C:\GSB (the folder with the GSB exes) and restart GSB.
3. New buyers: Peter recommends learning GSB without beta mode first. It's fully functional without it.
4. To turn it off, ask Peter. Trademaid hasn't confirmed whether deleting mode.txt is the way.

Why it happens

Almost always a set-up problem rather than a bug. If hours pass without a single system, something in the settings or data is wrong.

How to fix it

1. Wait a few minutes first. The manager takes about 2 minutes to start its workers.
2. If the status top right stays on searching, no worker is available. Start at least one worker on your own PC through Resource Manager, and make sure it uses the same share key as the manager.
3. If fitness shows 0, something drastic is wrong, such as the market-on-close time or last bar falling before the session opens. Check the session and Contracts List Last Bar time.
4. Make sure at least one secondary filter that suits the market is enabled. GSB needs one.
5. As a test, set costs to zero and loosen every filter except Test PF (about 1.1).
6. Load 5+ years of data, enough for about 100 trades, and check the file's symbol matches Data1 and is in the Contracts List.
7. Using 1-minute data? Set Mult. to the bar size you want (for example 30), not 1.
8. Still nothing? Load a different, known-good Opt Settings file (one of the supplied defaults) to rule out a bad settings file.

Why it happens

No worker is available. With no local worker running, the manager looks for cloud workers, which may all be busy.

How to fix it

1. Start at least one worker on your own PC through Resource Manager.
2. If you use a private share key, make sure every worker uses the same key as the manager.
3. Make sure managers and workers are on the same GSB build.

Why it happens

Often normal: some supplied set-ups only ever put a few systems in Favorites D. Very tight filters, or nearly every option switched on, can also leave it empty. Results also vary from run to run because each run uses a random seed.

How to fix it

1. Look in Favorites C as well.
2. Repeat the run. One run is not enough to judge a setting.
3. Go back to the supplied default settings and change one thing at a time.

Why it happens

Usually a cloud problem: workers were lost or the GSB cloud had an outage. Low resources or a build limit (Max. Run Time, max computations) can also cut it short.

How to fix it

1. Check Max. Run Time and the computations limit in your settings.
2. Reboot, then restart the manager and workers once the cloud is back.
3. Use local workers or a private share key for important runs.

Why it happens

A bug in the new build, or your saved Opt Settings don't suit it.

How to fix it

1. Load the default or another supplied Opt Settings file and test.
2. If that builds, re-create your own settings from the defaults.
3. If nothing builds at all, report it in the forum and run the previous build in the meantime.

Why it happens

Windows or the .NET Framework is damaged, or the PC ran out of memory. The Windows event log tells you which.

How to fix it

1. Open Event Viewer → Windows Logs → Application and find the error at the time of the crash.
2. If it's a .NET runtime error, repair the .NET Framework (GSB needs 4.8) or repair Windows.
3. If the log shows low memory, see the out-of-memory entry: run fewer workers and enlarge the page file.
4. If it keeps happening, email the details to Peter or ask in the forum.

Why it happens

GSB writes every error to C:\GSB\Exceptions (and to each worker's own exceptions folder). A few exceptions in a large build are usually harmless, such as brief database or connection errors, and GSB carries on.

How to fix it

1. If a big build throws only a handful of exceptions and keeps going, let it finish.
2. SQL timeouts on workers ("The wait operation timed out") can be ignored. GSB retries.
3. If the same exception repeats every run, zip the files in C:\GSB\Exceptions and the worker exception folders and send them to Peter, or post in the forum.

Why it happens

Settings saved in an older build, or a bug in that build. "Custom indicator not found" can appear even when you have no custom indicators loaded. Metrics may drop to zero when you click the system.

How to fix it

1. Load the default optimisation settings (or right-click → Reset Optimization Settings), then reapply your changes one at a time.
2. Don't click the grid while a build is still sending systems.
3. Update to the newest build through Resource Manager. Several of these were fixed in later builds.
4. If it persists, send Peter the files in C:\GSB\Exceptions and the worker exception folders.

Why it happens

Usually a price file the settings refer to isn't in the loaded data or the Contracts List.

How to fix it

1. Check every Data1 and Data2 file in the settings is loaded and has a row in Tools → Contracts List.
2. If it still happens, zip the settings and data as a .7z file and send them to Peter.

Why it happens

GSB has run out of memory. It keeps all its calculations in RAM.

How to fix it

1. Run fewer workers, or let Resource Manager start and stop them for you.
2. Set the Windows page file to 50 GB minimum and 100 GB maximum, then reboot.
3. Add RAM if you can. 16 GB works, but only just.

Why it happens

Not enough RAM or virtual memory. Each worker can use 10 to 12 GB on 30-minute day-session data, and far more on 23-hour data.

How to fix it

1. Watch Machine Resources (System RAM %) during a run.
2. Run fewer workers than your RAM allows, and keep Resource Manager running so it closes and reopens workers as memory changes.
3. Set the Windows page file to 50 GB minimum and 100 GB maximum, then reboot.
4. Use one normalisation mode at a time: two modes double each worker's RAM.
5. Use fewer data streams, and larger bars where your method allows.

Why it happens

Usually settings: every indicator switched on, several normalisation or entry modes at once, many data streams, small bars, or different costs for fitness and reports (which makes GSB calculate every metric twice). Some markets, such as CL, are simply slower.

How to fix it

1. Keep fitness and report commission and slippage the same.
2. Use the supplied indicator set rather than switching everything on.
3. Enable one normalisation mode and one entry mode at a time.
4. Use fewer data streams and larger bars where your method allows.
5. A very slow first build on a new market is a warning sign. Start from the closest supplied market's defaults and check the session and secondary filter.

Why it happens

The PC has no spare RAM or CPU, every core is given to GSB, or the CPU is running too hot.

How to fix it

1. In App Settings, leave some cores unallocated.
2. Turn off the live top/latest updates in the window during long runs.
3. Keep the CPU below about 80 °C.
4. Don't change anything in GSB while a macro is running.
5. Reboot.

Why it happens

The manager checks the GSB cloud database when it starts, even with no cloud workers. If Trademaid's server is down, it can hang.

How to fix it

1. Kill the manager in Task Manager.
2. Check the Beta Builds thread in the forum for outage news, and wait for it to end.
3. Restart the managers and workers. Use Standalone in the meantime.

Why it happens

Windows 11 (and some later Windows 10 updates) gives background windows very low CPU priority. Some monitoring tools also misreport each worker's CPU use.

How to fix it

1. In Resource Manager, start workers in tiled mode (StartWorker Tiled = True), or bring the worker windows to the front.
2. Update Resource Manager. Later builds improved Windows 11 performance.
3. Trust Windows Task Manager's CPU figures. Tools such as Process Lasso may need adjusting.

Why it happens

Usually the CPU overheating under full GSB load.

How to fix it

1. Check the Windows event logs at the time of the reset.
2. Check the CPU temperature and keep it under about 80 °C. Better cooling is the real fix.
3. Resource Manager can throttle workers on temperature if you run it as administrator with temperature monitoring enabled.

Why it happens

Clicking re-backtests the system on the current settings. If you changed dates, Nth or other left-panel settings after the build, loaded the wrong .gsboptset, or the manager and worker builds differ, the numbers change. Corrupt settings can also cause it.

How to fix it

1. Select all systems → right-click → Override Original Settings to re-backtest everything on the current settings.
2. Load the .gsboptset the systems were built with before loading the systems.
3. Compare the Manager's GSB Version and Worker's GSB Version lines in the exported code.
4. Reset the opt settings to default, or test with one local worker or in Standalone.
5. In a macro that changes dates, make a backtest the last step before exporting stats.

Why it happens

By design. Each genetic run uses a random seed.

How to fix it

1. Repeat a test 4 or more times and compare the averages.
2. Don't judge a setting on a single run.

Why it happens

Windows is set to a European number format, with a comma as the decimal point.

How to fix it

1. Set Windows regional number formats to US (a full stop as the decimal point).
2. Restart GSB and GSB Automation.

Why it happens

New features often default to on, so an old .gsboptset can behave differently in a new build.

How to fix it

1. Open the old file in the new manager and save it under a new name.
2. Compare the two files with a diff tool to see what changed.
3. Or right-click → Reset Optimization Settings and rebuild your settings from the defaults.

Why it happens

Builds differ in features and compatibility rules. Editing an indicator's parameter ranges also breaks compatibility with saved systems.

How to fix it

1. Keep using the build the systems were made with while it's still valid.
2. From build 75.94, saved systems keep the compatibility rules of the build that created them, so update.
3. Don't edit parameter ranges if you rely on saved systems.

Why it happens

Workers take their settings from the manager a few minutes after it starts. Old settings can linger.

How to fix it

1. After a big Opt Settings change (such as a new data symbol), restart the manager and the workers.
2. Change nothing on a worker except the share key and, optionally, the cache size.
3. The exception: custom price-file date or time formats must be added to the workers' App Settings too.

Why it happens

A setting holds a value GSB can't handle, for example a Tab typed as the data separator.

How to fix it

1. Close GSB in Task Manager.
2. Temporarily move your app or opt settings file somewhere else so GSB starts on defaults.
3. Re-enter the setting correctly (a tab separator is written \t), or copy that section from another settings file.

Why it happens

A long-standing cosmetic bug. Nothing is actually wrong.

How to fix it

1. Ignore it. It doesn't affect building or results.

Why it happens

Each build expires after about 3 months, and GSB needs internet access to check. Occasionally everyone sees it straight after an update because of a fault on Trademaid's side.

How to fix it

1. Update managers and workers through Resource Manager.
2. If many users see it at once, wait a few hours and check the Beta Builds thread in the forum for a fix.
3. Without internet you're limited to Standalone.

Why it happens

GSB needs at least one secondary filter enabled.

How to fix it

1. Enable one secondary filter that suits the market (one at a time is best).
2. The supplied settings for each market show which filter is normally used.

Why it happens

You can't force more indicators than # of indicators (3 by default).

How to fix it

1. Force no more indicators than the indicator count.
2. Better still, don't force indicators at all. It defeats GSB's search.

Why it happens

Low system resources, or a build limit such as Max. Run Time (minutes) or max computations cutting the build short.

How to fix it

1. Check Max. Run Time and the computations limit.
2. Reboot and try again.
3. The default of 2,500 systems is enough. There's no need to go higher.

Why it happens

Changing something in GSB while a macro runs can lock it up.

How to fix it

1. Don't touch GSB while a macro runs.
2. To recover, press Stop, right-click Stop, then right-click → Cancel Active Tasks, and wait.
3. A cancel only takes effect when the current task finishes. A 60-second delay at the start of a macro gives you a window to cancel.

Why it happens

The macro was made for a different GSB build.

How to fix it

1. Get fresh macros. Resource Manager downloads updated ones.
2. Make sure they're in C:\GSB\Data\Settings\Macros.

Why it happens

Some macros were missing from some installs.

How to fix it

1. Let Resource Manager update. It downloads macros.
2. If the macro is still missing, ask in the General support questions thread; Peter has posted the files there before.
3. Don't swap in a similar-looking macro without checking its steps.

Why it happens

GSB reads the symbol from the start of the file name, and that symbol has no row in the Contracts List. Or the file name has a space in it, so GSB reads the whole name as the symbol.

How to fix it

1. Name the file symbol.interval.bartype.anything.txt with no spaces, for example ES.30.Minute.0830-1500CentralTime.txt.
2. Add the symbol in Tools → Contracts List (right-click a similar row → Clone, then edit it).
3. Load the data again.

Why it happens

GSB takes point values from its own Contracts List, so every secondary symbol, including cash indices such as $SPX.X, needs a row.

How to fix it

1. Add every symbol you use as Data2 or Data3 to the Contracts List.
2. Give a cash index the same point value as its future.

Why it happens

The Contracts List Last Bar (market-on-close) time doesn't match the last bar of the day in your file.

How to fix it

1. Open the .txt file and find the time of the last bar of the day.
2. Set the contract's Last Bar to that time (for example 1500 for ES 8:30 to 15:00).
3. Use the bar time as it appears in your file. GSB doesn't care whether it's local or exchange time.

Why it happens

The file format isn't what GSB expects: newest bar first, extra columns from chart indicators, or a date or time format GSB doesn't recognise.

How to fix it

1. Export oldest bar first.
2. Remove all indicators from the chart before exporting. Columns should be Date, Time, Open, High, Low, Close, Volume.
3. Forex files need a volume column too.
4. For an unusual date or time format, add it in Tools → App Settings → Data → Price Files Date Formats / Time Formats (capital M is month, small m is minute).

Why it happens

A date or time format GSB doesn't recognise. Custom formats added in the manager's App Settings aren't automatically on the workers.

How to fix it

1. Add the format in Tools → App Settings → Data → Price Files Date Formats / Time Formats.
2. Add the same format to every worker's App Settings.
3. Update GSB: build 75.94 recognises more date formats.

Why it happens

The price-data list or contracts file is corrupt.

How to fix it

1. Back up the bad file.
2. Copy a known-good copy, or the default from C:\GSB\Data, into each settings folder that uses it.
3. Send Peter the bad file so he can trap the error.

Why it happens

Data streams on different time zones let one stream look into the future. US and other countries also change daylight saving on different dates.

How to fix it

1. Put every data stream on the same time zone, and match the session times of primary and secondary data.
2. With US and European data together, leave out the roughly two weeks a year when daylight saving doesn't line up.
3. Trading from outside the US? Running the trading PC on US Central time avoids most daylight-saving problems.

Why it happens

GSB session and MOC times are in the time of your exported data. For TradeStation and MultiCharts exports that's usually your PC's local time, not the exchange time shown on the chart.

How to fix it

1. Check the times of the bars in your data file and use those.
2. MultiCharts example: a PC on Eastern time with ES 8:30 to 15:00 Central gets MOC 16:00 in GSB.
3. Every data stream in the workspace must use the same time basis.

Why it happens

Before build 75.94 the default session for new price files was 24/7, which TradeStation can't reproduce. Some 24-hour feeds also added weekend bars.

How to fix it

1. Use a 24/5 session (the default since 75.94) or one of the built-in exchange sessions.
2. Update to 75.94 or later for the weekend-bar fix.

Why it happens

Data2 and Data3 must be the same bar size as Data1, or a whole multiple of it, never smaller. TradeStation only calculates when both bars close together.

How to fix it

1. Use a whole multiple of Data1's bar size for Data2 (for example 30 and 60, not 30 and 29).
2. Building on several intervals? Click the interval you'll trade first.

Why it happens

From build 66.25, any multiplier above 1 must start from 1-minute data.

How to fix it

1. Load 1-minute data and set Mult. to the bar size you want.
2. Or load the 30-minute file with Mult. set to 1.

Why it happens

Market On Close is set to True, which doesn't work with daily bars.

How to fix it

1. Set Market On Close = False for daily data.
2. Make sure the symbol has a Contracts List row.
3. From build 75.94, Day, Week and Month bars are supported as primary data, and an Add Day Data button helps.

Why it happens

In the Contracts List, Ticks means ticks per point (ES = 4), not tick size. Digits is decimal places. Point value matters unless you use Capital Investment quantity mode.

How to fix it

1. Take the values from your platform's symbol properties.
2. Or right-click a similar row → Clone and edit it.

Why it happens

A TradeStation data issue, often after an outage or with unusual continuous symbols.

How to fix it

1. Use the standard continuous symbol (for example @CL) with symbol substitution.
2. Refresh the chart with Ctrl+R, or close TradeStation and delete its cache.
3. After an outage, check for data holes before rebuilding or comparing. If a hole stays, contact TradeStation.

Why it happens

Your GSB functions (ELD) are older than the GSB build that exported the code. That first line only checks the matching functions are loaded.

How to fix it

1. Import the dated GSB_ALL_FUNCTIONS_YYYY_MM_DD.ELD from C:\GSB\Supplementary Scripts (TS & MC) (MultiCharts users import the .pla).
2. From build 76.35, GSB can export the matching ELD or PLA for you.
3. If the newest ELD doesn't contain the function, ask in the forum. You can comment out the dummy line meanwhile, but the new ELD usually has other updates you need.

Why it happens

The GSB functions in your platform are missing, old, or failed to import. Occasionally a brand-new GSB feature has no TradeStation version yet.

How to fix it

1. Import the latest GSB functions file and Verify All.
2. If one brand-new filter or indicator is the only unknown function, report it in the forum and rebuild without it meanwhile.

Why it happens

The imported function is empty after a failed import.

How to fix it

1. Re-import the GSB functions file and verify again.

Why it happens

A bug in scripts exported in early 2026 left an uncommented calculation with Plot lines at the end. Plot statements can't be used in a strategy.

How to fix it

1. Comment out or delete the plot lines at the bottom of the strategy.
2. Update GSB. If your current build still does it, report it in the forum.

Why it happens

A bug fixed in build 75.94.

How to fix it

1. Update to 75.94 or later.
2. Meanwhile, delete the trailing comma.

Why it happens

Maximum bars referenced isn't set to 500, or the chart doesn't have enough history or the right session.

How to fix it

1. Set Maximum number of bars study will reference to 500 (Properties for All → General).
2. Import the latest ELD and Verify All.
3. Load several years of data with the correct session.

Why it happens

The chart is missing a data stream the code uses.

How to fix it

1. Look at the // Price Data: line at the top of the script.
2. Add every listed stream to the chart in that order (for example ES + $IDX + $SPX.X = three streams).

Why it happens

Usually too little history or holes in the chart data, not the ELD itself.

How to fix it

1. Load at least 3 years of data with no holes.
2. Refresh the data with Ctrl+R, or close TradeStation and delete its cache.
3. Try the same system on other data to see whether it's the data.
4. Still happening? Ask in the forum.

Why it happens

An indicator returned an invalid number on some bars, often from bad data or an old function version.

How to fix it

1. Import the latest GSB functions ELD.
2. Check the data for bad bars and refresh it.
3. If it continues, ask in the forum with the system and data.

Why it happens

TradeStation's installation or cache is damaged. GSB code is very unlikely to cause it.

How to fix it

1. Windows Settings → Apps → TradeStation → Change → Repair.
2. Delete the TradeStation cache, then reload your workspaces.
3. Contact TradeStation support if it keeps happening.

Why it happens

From build 70.58, the TradeStation functions use object-oriented EasyLanguage that MultiCharts doesn't support, so MultiCharts needs its own .pla. MultiCharts code doesn't work in TradeStation either.

How to fix it

1. Copy the script for your platform from GSB's Scripts tab.
2. Import the MultiCharts .pla (_MC.pla), not the ELD.
3. Update GSB: later builds fixed exports to the MultiCharts .pla.

Why it happens

Each GSB build expects functions at least as new as itself. From build 76.35, GSB can export the matching ELD (TradeStation) or PLA (MultiCharts) itself.

How to fix it

1. On 76.35 or later, export the functions from GSB and import them into your platform.
2. On older builds, use the dated file in C:\GSB\Supplementary Scripts (TS & MC).
3. Verify all functions after importing.

Why it happens

A known MultiCharts issue, often permissions or the install path.

How to fix it

1. Run MultiCharts as administrator and recompile.
2. Check the MultiCharts install path.
3. If that fails, contact MultiCharts support.

Why it happens

Old GSB code included leftover debug lines and legacy functions such as GSB_Norm2.

How to fix it

1. Re-export the system with a current GSB build.
2. Or delete the External: DLL line and any Norm2 call.

Why it happens

Your GSB NinjaScript Add-On is older than the GSB build that exported the strategy.

How to fix it

1. Import the matching or newer GSB_NinjaScript_yyyy_mm_dd Add-On (Tools → Import → NinjaScript Add-On).
2. Compile LibGSB, then the strategy.

Why it happens

The target platform isn't set to NinjaTrader, or a setting only TradeStation supports is in use. NinjaTrader support was extended a lot in builds 75.94 and 76.35.

How to fix it

1. Set Tools → Preferred Target Platform to NinjaTrader, then build, so only NinjaTrader-compatible items are used.
2. Update to 76.35 or later.
3. If there's still no NinjaTrader code, ask in the forum which setting is blocking it.

Why it happens

You pasted new GSB code into a strategy already on a chart, so the platform kept the old input values. This is one of the most common mistakes.

How to fix it

1. Always insert a new strategy with a new name for each system.
2. Export as vars: (the default). Change to inputs: only when you want to optimise in the platform.

Why it happens

Usually the session or time zone, then bars back, data, bar interval or costs.

How to fix it

1. Match the session. For ES, NQ, EMD and ER use 8:30 to 15:00 Central, not 15:15.
2. Set maximum bars back to 500, and use the same bar interval, slippage and commission.
3. Put all data streams on one chart and export from that chart, with volume as Tick Count.
4. Stop new entries before the last bar of the session.
5. Run MatchCheck (Tester Settings → Match-Check) to find which systems and indicators differ.

Why it happens

Normal. Calculations only start after 500 bars, and data caches and rollovers differ slightly between GSB and the platform.

How to fix it

1. A 98 to 99% match is expected.
2. Check the yearly breakdown to see where results differ.

Why it happens

GSB data from TradeStation should use volume as Tick Count. Feeds such as IQFeed and NinjaTrader history have total volume only, so volume-based indicators differ.

How to fix it

1. Export TradeStation data with volume set to Tick Count.
2. Build on the same feed you'll trade.

Why it happens

The data time zone in GSB differs from the chart's. Adding SetExitOnClose only hides the problem.

How to fix it

1. Check the data was exported on the same time basis as the chart.
2. Recheck the Contracts List Last Bar time against your data.
3. Remember GSB times are in the time of your exported data, not the exchange time on the chart.

Why it happens

Corrupt MultiCharts symbol data, session template or cache.

How to fix it

1. Delete the symbol, its data, the session template and the symbol cache, then recreate them.
2. As a last resort, reinstall MultiCharts.

Why it happens

Older EWFO builds have a built-in expiry, and auto-update often failed (usually for lack of admin rights), so paid users were left on an expired build.

How to fix it

1. Download the newest installer from Trademaid's EWFO page. Installing it keeps your licence.
2. Run EWFO once as administrator so its auto-update can work.
3. Still says expired? Email Peter at peterzwag@gmail.com.

Why it happens

Older installs went into C:\Program Files (x86)\EWFO, where EWFO can't update itself without admin rights. Current installers use C:\EWFO and are digitally signed, but Windows may still warn about a new download.

How to fix it

1. If Windows Defender SmartScreen warns, click More info → Run anyway.
2. Install to C:\EWFO.
3. On an old install, run EWFO as administrator, or copy its files to C:\EWFO and point your shortcut at C:\EWFO\WalkForwardOptimizer.exe.

Why it happens

A bug in older PA Pro trial builds, fixed in March 2024.

How to fix it

1. Download the current PA Pro from Trademaid's PA Pro page and install it.
2. If it still shows expired, you may have used a trial on this PC before. Email Peter to ask for an extension.

Why it happens

An earlier update file contained registration info and reset some users' activation. Peter says that's no longer in update files.

How to fix it

1. Don't keep re-activating, which uses up activations.
2. Email Peter at peterzwag@gmail.com. He revokes the licence so you can activate it again.

Why it happens

Either a real build expiry, or (in 2024) a false warning caused by a bug.

How to fix it

1. Click OK. If PA Pro carries on working, it was the false warning and you can ignore it.
2. If it closes, right-click PA Pro → Run as administrator and let it update.
3. Or reinstall from Trademaid's PA Pro page.

Why it happens

The shortcut may start the old, non-Pro Portfolio Analyst (a different program), you may be on an old build with a known crash, or a trial was already used on this PC.

How to fix it

1. Point your shortcut at PA Pro's exe in C:\papro.
2. Install the latest PA Pro from Trademaid's PA Pro page.
3. If it's a trial already used on this PC, ask Peter to extend it.
4. To open the activation window on purpose, hold Shift while starting PA Pro. If that doesn't bring it up, ask Peter.

Why it happens

GSB Automation can't work with a trial GSB, because trial managers always show the days-left prompt. Its own 14-day trial starts after you buy GSB.

How to fix it

1. Buy GSB first, then ask Trademaid for the GSB Automation trial.
2. Use your GSB trial to learn the manual workflow, which Automation runs for you later.

Why it happens

It was installed straight into C:\GSB, alongside the GSB exes, where its files clash with GSB's.

How to fix it

1. Install GSB Automation to C:\GSB\GSB_AUTOMATION, never the folder holding the GSB exes.
2. Run install-into-GSB.bat to copy the macros. If you have custom sessions, back up sessions.txt first or skip the batch file's last step.
3. If GSB is already broken, let Resource Manager update GSB again with everything closed.

Why it happens

The installer in the buyers' thread (tid 267) is the original build. Updates and the Excel spreadsheet come from the pCloud link Peter sends purchasers.

How to fix it

1. Install from tid 267, then copy the latest files from your pCloud link over that install.
2. If the pCloud zip seems broken, download it again later.
3. Lost the pCloud link, or the zip is still broken? Email Peter at peterzwag@gmail.com.

Why it happens

Automation only updates when all its windows are closed, needs the most recent GSB build, and can only drive a GSB Manager (not Standalone).

How to fix it

1. Close every Automation window and reopen it.
2. Or copy the new GSBAutomationYYYYMMDD.exe, its .pdb and version.txt, and point your shortcut at the new exe.
3. Update GSB through Resource Manager.
4. If Automation opens the old GSB after a major update, set Path Mode to exe.

Why it happens

EWFO loads the optimisation files into RAM.

How to fix it

1. Enlarge the Windows page file and reboot.
2. Run C:\GSB\ResourceMonitor\ReduceMemory.exe.
3. Use fewer iterations or larger steps in the optimisation.
4. Add RAM.

Why it happens

EWFO is installed under Program Files and running without admin rights.

How to fix it

1. Run EWFO as administrator.
2. Or copy it to C:\EWFO and point the shortcut at C:\EWFO\WalkForwardOptimizer.exe.

Why it happens

Data Filters are hiding the results. Stability scores re-run a whole walk-forward per fitness, which takes time.

How to fix it

1. Check or untick Data Filters.
2. Wait if it pauses at about 87%.
3. Still empty means no fitness worked on this system.

Why it happens

The files were written by an old GSB build, or a price file is missing from the data.

How to fix it

1. Regenerate the walk-forward files with a current GSB build.
2. Try a different end date.
3. If it persists, send the files to Peter or ask in the forum.

Why it happens

Usually a damaged file (for example from a crashed TradeStation optimisation) or an old EWFO build.

How to fix it

1. Update EWFO.
2. Re-run the TradeStation optimisation. A file from a crashed run is damaged, but stopping a run yourself is fine.
3. If it still hangs, zip the performance report and data files as .7z and send them to Peter with screenshots.

Why it happens

The wrong optimisation type, or the EWFO function isn't in the strategy code.

How to fix it

1. Tick the Walk Forward box and use Genetic or Exhaustive optimisation.
2. Add the EWFO function to your strategy code, following the MultiCharts set-up steps.

Why it happens

TradeStation can't write to the folder in the strategy, usually under Program Files, or the path is wrong (older strategies used a folder without "Pro").

How to fix it

1. Use the current PA Pro ELD, which installs to C:\papro.
2. Or run TradeStation as administrator.
3. Or change the fname path in the strategy to a folder that exists.

Why it happens

The .pa file writes trades in time order, so real pyramiding systems can't be read. Some files were wrongly flagged in late 2025 builds.

How to fix it

1. For systems that really pyramid, use the XML export instead.
2. If the system doesn't pyramid, update PA Pro, then zip the .pa file and the XML report from the same system and send them to Peter.
3. To find a bad file among many, load half your systems, then keep halving.

Why it happens

It's installed under Program Files and running without admin rights.

How to fix it

1. Run PA Pro as administrator once.
2. Or reinstall it into C:\papro.

Why it happens

Later TradeStation 10 builds removed XML performance export, and some older GSB builds wrote faulty .pa files.

How to fix it

1. Use the PortfolioAnalyst ELD exporter (.pa files) from C:\papro\TradestationCode.
2. Update GSB if its Export to Portfolio Analyst option writes nothing or bad files.
3. PA Pro says it is too old? Install the latest version.

Why it happens

Daily bars have no intraday highs and lows, so intraday drawdown can't be calculated exactly.

How to fix it

1. Treat the drawdown figures as approximate.
2. Or use an XML report instead of .pa files where your platform can make one.

Why it happens

The macros named in Automation aren't in GSB's macro folder. GSB shows no message, only an exception file.

How to fix it

1. Copy the macros from Automation's MacrosToAddIntoGSBMacroFolder into C:\GSB\Data\Settings\Macros, or run C:\GSB\GSB_AUTOMATION\install-into-GSB.bat (back up sessions.txt first, as the last step overwrites it).
2. Select the macros again in Automation.
3. Check C:\GSB\Exceptions for details.

Why it happens

Some secondary filters produce no systems, and the manager never finishes.

How to fix it

1. Set the Automation timeout to about twice the time a manager normally takes.

Why it happens

Import Loops is above 0, but no earlier pass has exported its indicators to C:\GSB\Data\Exports\IndicatorsUsed.

How to fix it

1. Make sure an indicator build pass ran and exported first.
2. Or set Import Loops to 0.

Why it happens

A file-name mismatch: special characters or spaces in names, a different name from the one Automation expects, or settings saved somewhere else.

How to fix it

1. Save opt settings in C:\GSB\Data\Settings\Optimization\Manager.
2. Avoid spaces and special characters in names.
3. Do a quick end-to-end test with tiny builds before starting a long queue.

Why it happens

Automation uses spaces to separate command-line items.

How to fix it

1. Use names without spaces or special characters (for example GCv1), or put the text in quotes.

Why it happens

Automation can still point at the old manager, and new managers won't talk to old workers.

How to fix it

1. Set Path Mode to exe and point it at the new manager.
2. Stop running jobs before a major update.
3. Logs are in %AppData%\GSB Automation\log.

Why it happens

Only a GSB Manager can be driven. If the indicator-build step fails, the following build steps abort by design.

How to fix it

1. Select a Manager, not Standalone.
2. Fix the indicator-build failure first, then rerun.

Why it happens

SetExitOnClose can fail live in TradeStation 10 unless the session ends at the standard close.

How to fix it

1. Add an explicit end-of-day exit, for example: vars: eod(0); once eod = SessionEndTime(0,1); if Time = eod and CurrentContracts > 0 then begin Sell ("LX_EOD") this bar at close; Buy to cover ("SX_EOD") this bar at close; end;
2. Or use Trademaid Automation (TMA), which handles exits itself.

Why it happens

A fixed-time exit can't fire after an early close.

How to fix it

1. Simplest: don't run day-trading systems on half days.
2. Or block entries with the holiday1/holiday2 inputs or HolidayNHalfDay(date).
3. With TMA, set an earlier market-on-close time for that day.
4. As a fallback, exit any position left over at the next day's open.

Why it happens

TradeStation recalculates the previous close at about 8:30 to 8:31 am Central.

How to fix it

1. At about 8:31 Central, press Ctrl+R on every daily-bar symbol (for example @ES.D).
2. Check each chart reloaded with its trades.

Why it happens

TradeStation rejects orders on continuous symbols, data streams can drift onto different contracts, and broker roll dates differ from TradeStation's.

How to fix it

1. Key charts off the continuous symbol and use symbol substitution (needs TMA on TradeStation).
2. Otherwise put the same specific contract on every stream.
3. Roll CL early. Trademaid posts yearly rollover dates in the forum.

Why it happens

TradeStation's historical and real-time data differ, or the strategy is stuck. A strategy active on the chart but missing from Trade Manager's Strategy Positions tab is the tell-tale sign.

How to fix it

1. Toggle the strategy's Status off and on (don't use chart Reload).
2. Key charts off the continuous symbol (for example @ES.D), not a dated contract.
3. Re-check positions after the close. A second TradeStation copy for comparison helps.

Why it happens

Memory leaks, too many charts, long histories, a damaged cache or workspace, or forced updates.

How to fix it

1. Restart TradeStation daily.
2. Keep about 48 charts or fewer per instance, and about 1 year of history.
3. Use AnyDesk rather than Remote Desktop.
4. Stay on a stable TradeStation build, and repair the install or delete the cache only when there's a problem.

Why it happens

Alertmon and TMA use your PC's local time, not chart time. Alertmon can also keep an old session time.

How to fix it

1. Enter session end times in local PC time (an Eastern PC with a 16:00 Central bar needs 17:00).
2. In Alertmon, set always update session time to True.

Why it happens

GSB code places stops from TradeStation's theoretical entry price, not your actual fill.

How to fix it

1. Expect small differences when your entry slips.
2. Consider sending strategy stop orders to the TradeStation server, so they survive a PC or VPS dropout.

Why it happens

One system's resting stop or target opposes another system's order on the same symbol.

How to fix it

1. Stagger exit times by a few seconds (TMA does this for you).

Why it happens

Buy pages need a gsbpro.com login so we can email you the after-purchase checklist. You still pay Trademaid, not GSB Pro.

How to fix it

1. New here: fill in the short form; you come back to the Buy page automatically.
2. Already have an account: enter your email anyway and click Log in now when it says you have one, or log in from the header and click Buy again.

Why it happens

Trademaid opens in a new tab so gsbpro.com stays open with your next steps. The tab may be behind this window, or an in-app browser (from an email or social app) may block new tabs.

How to fix it

1. Look for a new tab or window on trademaid.info.
2. Click Open Trademaid again.
3. In an in-app browser, open gsbpro.com in Chrome, Safari or Edge instead.

Why it happens

More than 10 Buy-page clicks came from one internet address in 10 minutes. Trademaid still opens; only our record and checklist email are skipped.

How to fix it

1. Wait 10 minutes. You can still pay on Trademaid in the meantime.

Why it happens

A temporary error, or your login had run out.

How to fix it

1. Click the button again. Clicking it twice does no harm.
2. If you're sent to the login page, log in and click it again on Get the Software.
3. Still failing? Email the team.

Why it happens

gsbpro.com only knows you've bought when you click I've bought GSB on Get the Software. Buying an add-on doesn't change it. Your real licence is held by Trademaid, not gsbpro.com, so this doesn't affect GSB itself.

How to fix it

1. Go to Get the Software and click I've bought GSB.
2. Reload the page.
3. For the licence itself, check the emails from Trademaid.

Why it happens

Licences come from Trademaid (and its licensing service, SoftwareKey) by email, not from GSB Pro. Peter matches payments by hand, and a different PayPal email from your forum email can slow this down.

How to fix it

1. Search all mail folders (including spam) for Trademaid and SoftwareKey.
2. Allow for Australian day hours, Monday to Saturday.
3. Still nothing? Email Peter at peterzwag@gmail.com with your forum username, the email you paid with and the payment details. Don't post licence details in the forum.

Why it happens

Buyers must fill in and return Trademaid's NDA first. Trademaid won't give access to the private forum, systems or Resource Manager until it's done. Access is then turned on by hand, normally within one working day.

How to fix it

1. Follow the after-purchase steps and return the signed NDA.
2. Keep the trial installed: Resource Manager updates the existing GSB files.
3. After one working day, still locked out? Email Peter with your forum username and the email you paid with.

Why it happens

The checklist ("Your ... after-purchase checklist") is sent from noreply@updates.gsbpro.com when you click Continue to Trademaid on a Buy page. It often lands in spam or Promotions.

How to fix it

1. Search all folders for updates.gsbpro.com.
2. The same steps are in the Strategy Guide under After you buy.
3. Still want the email? Ask the team through the contact form.

Why it happens

GSB Pro doesn't sell software or take payments. Trademaid sells GSB and its add-ons under its own terms, and because GSB has a free 14-day trial, all sales of GSB are final.

How to fix it

1. Use the free trials (14 days for GSB, 21 days for EWFO) before you buy.
2. For a problem with a purchase, email Peter at peterzwag@gmail.com with your order details and licence ID.
3. Read the full policy on our refund page.

Why it happens

Trademaid's discount on extra GSB licences applies only when you buy them on the same day as your first GSB licence.

How to fix it

1. Decide how many PCs you'll build on before you buy, and buy the extras the same day.
2. Check current prices on Trademaid's purchase page, or ask Peter before buying.

Why it happens

Trademaid takes payment through PayPal buttons on its purchase page and also accepts bank transfers in some currencies. GSB Pro takes no payments.

How to fix it

1. Email Trademaid at info@trademaid.info for current exchange rates and transfer details.
2. Use only the payment details Trademaid gives you directly.