Share via

CAD software not working after Windows 11 August update

Reynald Kurniawan 20 Reputation points
2025-09-26T05:01:13.8533333+00:00

Hello, I'm currently using a software called NanoCAD free, which is almost like AutoCAD, but it's a free, unsupported version of the thing. After the Windows 11 August update, it just stopped working occasionally. It would start freezing for an endless amount of time, and the only way to fix it is to force quit it using Task Manager. But even after restart, the issue kept going. I'm currently on a non-admin account.

I've heard that the issue is because of the change in UAC from the August update which affects apps like AutoCAD. I assumed because the two apps are similar, they have the same problem. I've also already installed the September update which they say fixes the UAC problems, but there's been no change here. The app still froze over and over again. The only solution that helped so far is to roll back the Windows update itself. But this isn't a permanent solution since it'll reinstall sooner or later, so I need a permanent fix. I've read that putting the app in the allowlist that came with the September update might help. But I'm a little scared of messing with the registry. Can anyone help me? Thank you.

Windows for home | Windows 11 | Windows update
0 comments

Answer accepted by question author

  1. Anonymous
    2025-09-26T10:22:26.1033333+00:00

    Hello @Reynald Kurniawan !

    Thanks for reaching out this platform!

    From what you described, this doesn’t look like a random crash, it’s more likely a compatibility and lifecycle issue triggered by the Windows 11 August update. The fact that NanoCAD Free freezes consistently after the update, but works again when you roll back, strongly suggests that the UAC hardening and driver/runtime changes introduced in that patch are exposing weaknesses in NanoCAD’s unsupported runtime model.

    Since the issue is scoped to this specific app and update, here are the possible root causes I can give:

    • UAC hardening conflict: The August update changed how non‑admin apps request elevation. Legacy CAD apps (AutoCAD, NanoCAD Free) may hang instead of prompting.
    • Dependency/runtime mismatch: NanoCAD Free relies on older Visual C++ and .NET runtimes that may not load correctly after the update.
    • Graphics driver pipeline change: The update refreshed WDDM components; older OpenGL calls used by NanoCAD may stall.
    • Unsupported lifecycle: Because NanoCAD Free is no longer maintained, it won’t receive compatibility patches, so issues persist even after the September cumulative update.

    Recommended Fixes

    • Force elevated execution: 
        Right‑click nanocad.exe → Properties → Compatibility → Run this program as administrator
      This bypasses UAC deadlocks for many users.
    • Add to allowlist without registry edits:
      • Open Windows Security → App & browser control → Exploit protection → Program settings
      • Add nanocad.exe and disable “Force randomization” or “Mandatory ASLR” if present.
    • Reinstall runtimes:
      • Install latest Microsoft Visual C++ Redistributables (x86/x64, all years)
      • Confirm .NET Framework 4.8+ is present
    • Clean reinstall NanoCAD:
      • Uninstall NanoCAD, remove leftover folders in Program Files, ProgramData, and AppData\Roaming
      • Delete registry key: HKEY_CURRENT_USER\SOFTWARE\Nanosoft AS
      • Reinstall fresh
    • Update or roll back GPU drivers:
      • Get latest drivers from NVIDIA/AMD/Intel
      • If issue began after GPU update, roll back to prior stable version
    • Compatibility mode:
      • Run NanoCAD in Windows 8 or Windows 7 compatibility mode
    • Make sure you log whether NanoCAD only freezes on non‑admin accounts vs admin accounts.
    • You can check Event Viewer → Windows Logs → Application for nanocad.exe errors after freeze.
    • Track GPU driver version and runtime versions installed to confirm reproducibility.

    If you apply Run as Administrator and reinstall runtimes, and the issue disappears in long‑run tests, then it’s a UAC/runtime compatibility problem rather than a random glitch. If not, the safest long‑term path is either upgrading to a supported NanoCAD build or isolating NanoCAD Free in a Windows 10 VM.

    I hope this helps! Let me know if you have any questions

    1 person found this answer helpful.
    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.