AutoGraw Not Loading? Diagnose and Fix the Menu

Most missing-menu problems come from Tampermonkey being disabled, userscript permission being off, site access not covering the current page, an outdated or unofficial script, or testing on a page outside the supported McGraw Hill environments. Work through the checks below in order.

Identify the exact failure

Choose the description that matches what you see:

• No AutoGraw menu at all: focus on Tampermonkey, the installed script, site access, page matching, and extension conflicts.
• Menu appears but asks for a license: focus on key delivery, redemption, entitlement, and network access.
• Menu appears and the license is active, but one feature does nothing: focus on the specific page layout, feature settings, and supported question type.
• Menu is visible but stays in a loading state: capture the page, feature name, and browser console errors before refreshing.
• It worked earlier and suddenly stopped: record the installed versions and recent browser or page changes before reinstalling.

This distinction matters because the menu can load even when a backend request fails, and a valid key cannot make Tampermonkey inject a disabled script.

1. Confirm you are using a supported browser

The current public support list names Chrome, Edge, Brave, Opera, and other compatible Chromium-based desktop browsers. Safari, Firefox, and mobile browsers are not currently listed as supported.

Update the browser to a current stable version. If the device is managed by a school or employer, open the browser's management information. Organization policies can disable extensions, lock site permissions, or prevent userscripts from running. Only the administrator can change those policies.

2. Confirm Tampermonkey is enabled

Open the browser's extension-management page. For Chrome, use chrome://extensions/; for Edge, use edge://extensions/. Locate Tampermonkey and verify that its main toggle is on.

Then open Tampermonkey's dashboard and confirm that AutoGraw appears in the installed-scripts list with its own toggle enabled. If AutoGraw is missing from the list, return to the official AutoGraw download page and install the current userscript.

If the script file opens as plain text without an installation screen, Tampermonkey is not intercepting it. Recheck the extension state and userscript permission before downloading another copy.

3. Check userscript permission and site access

Chromium browsers can require explicit permission for userscript managers. Open Tampermonkey's extension details and enable the option that allows user scripts if it is present. Developer mode may also be required by the current browser configuration.

Next, inspect site access. Tampermonkey must be allowed to run on the current supported McGraw Hill page. AutoGraw's metadata includes McGraw Hill address families such as mheducation.com, mcgrawhill.com, and aleks.com, but the browser still controls whether Tampermonkey can inject the script.

After changing permissions, return to the page and perform a hard refresh with Ctrl + Shift + R on Windows or Command + Shift + R on macOS.

4. Test on an actual supported assignment page

AutoGraw is not expected to load on every school page. Your college portal, LMS dashboard, email, syllabus, or generic login page may appear before the browser reaches McGraw Hill content.

Launch the course through the normal school LMS route and open a supported McGraw Hill assignment. Wait for the activity itself to load, then refresh. If the menu appears there, the installation is working and the earlier page was simply outside its scope.

Support also depends on the page layout and assignment environment. The current implementation explicitly includes supported SmartBook and EZTO workflows, but it does not promise every essay, graph, simulation, external tool, or arbitrary activity.

5. Verify that the script is current and official

Open the AutoGraw entry in Tampermonkey and record its version before making changes. The public userscript audited on October 21, 2026 was version 1.75.75; a later official release may now exist.

Use the metadata and official download page to check for updates. The current official update and download address is https://autograw.com/autograw.user.js. Avoid copies from old chat attachments, mirrors, code-sharing sites, or “unlocked” downloads.

If you reinstall, use the official route and verify the script name and matched sites in Tampermonkey. Do not clear browser storage unless support specifically asks you to, because that can remove settings and useful evidence.

6. Rule out extension conflicts

Content blockers, privacy extensions, script blockers, security products, and other McGraw Hill tools can interfere with the same page. The cleanest test is a separate browser profile:

1. Create a temporary local browser profile.
2. Install only Tampermonkey from the official store.
3. Install AutoGraw from the official download page.
4. Sign into the school and open the same supported page.
5. Compare the result with the main profile.

If AutoGraw works in the clean profile, another extension or setting in the main profile is likely involved. Re-enable extensions one at a time rather than disabling security protections permanently.

7. Separate license problems from loading problems

If the menu appears, the userscript has loaded. A message about a missing, invalid, expired, or revoked key should be investigated through the account area and purchase record.

Paste the key without extra spaces. Confirm that it came from the AutoGraw success page or purchase email, and check whether the subscription is still active. Do not post the key in Discord screenshots.

If the key is valid but the menu cannot reach the validation service, record the exact error and test whether another network, VPN setting, firewall, or privacy tool changes the result. Do not repeatedly redeem the same key without capturing the first failure.

8. Diagnose a feature that stays loading

When the menu and license work but a feature does not, record:

• Feature name
• Assignment environment
• Question type
• Visible page state
• AutoGraw version
• Browser version
• Whether Manual Fallback is enabled
• Exact loading or error text

Try a supported simple question type before concluding that the entire script is broken. A single unrecognized matching, graph, simulation, or embedded activity can require manual completion even while other supported questions work.

If the feature has an expandable settings panel, confirm that its required setting is present and saved. Do not assume that enabling a top-level toggle automatically configures every dependent option.

9. Capture useful information for support

Before contacting support, collect:

1. Browser name and version
2. Operating system and version
3. AutoGraw userscript version
4. Full current page URL
5. Whether Tampermonkey shows AutoGraw as running on that page
6. Exact feature or stage that failed
7. Exact error text
8. A screenshot with name, school ID, grades, course details, and license key removed

Use the official AutoGraw Discord. A precise report makes it possible to distinguish a new page layout from a local permission issue.

What not to do

Do not download a modified userscript from an unknown source. Do not publish your license key. Do not erase all browser data before saving evidence. Do not test a major change for the first time during a timed assessment. And do not assume a tool is allowed merely because it can technically run—follow the course and institution rules.

For a clean installation from the beginning, follow the complete AutoGraw setup guide.