Somewhere on a shared drive there is a folder called TRAINING_FINAL_v3, and inside it sits an .exe built in Authorware. It probably still has a job. A safety induction, a product walkthrough, a module someone must prove people took. Nobody wants to be the person who double-clicks it on a new laptop. Can you still run Authorware courses, and what should you do with them if you can't?

Sometimes, on some machines, for a while, and that is not a plan. Some 32-bit packaged Authorware pieces will still launch on modern Windows with coaxing. 16-bit builds will not run on 64-bit Windows at all, and the web-packaged versions need a browser plugin that current browsers no longer load. Adobe stopped developing Authorware in 2007, so nothing is getting fixed. Your real options are to contain a copy for reference, convert the content into a modern format, or rebuild the parts that matter. Most libraries end up using all three.

What Happened to Authorware After Adobe Stopped Developing It?

It froze. Authorware came from Macromedia, passed to Adobe with the rest of Macromedia's products, and Adobe announced the end of Authorware development on August 3, 2007. The last version was 7.02. No new releases, no patches, no support for the Windows versions that came after.

Can You Still Run Authorware Courses? – What to Do With Training Built in a Tool Adobe Stopped Developing - 3D Cutaway Animation

That matters because Authorware was never just a file format. It was a runtime. You built a course on a flowline of icons (display, interaction, calculation, decision, map, framework), and the packager either bundled the runtime into a standalone .exe or produced a runtime-dependent file that needed a separate player. For the web, it produced map and segment files streamed through a browser plugin. Every one of those routes depends on software frozen at a point when most offices ran Windows XP.

So when people ask about Authorware end of life, the honest answer is that the end already happened. What you have left is a slow drift as the world around the frozen runtime keeps changing.

Will Authorware Courses Still Run on Modern Windows?

Some will, some won't, and you find out by testing, not by asking around. The first split is age. Very old pieces packaged as 16-bit programs will not start on 64-bit Windows, full stop. Pieces packaged from later 32-bit versions often do start. Starting is not the same as working, though.

The failures that show up on a modern machine are boringly consistent:

  • Missing Xtras. Authorware leaned on plug-in modules called Xtras for media, transitions and file handling. If the packaged folder lost its Xtras subfolder, you get blank screens or an error on launch.
  • Hard-coded paths. The piece looks for media on a drive letter or network share that died years ago.
  • Permission problems. It tries to write a bookmark or score file next to itself, and modern Windows says no.
  • A postage-stamp window. Many pieces were built at 640 by 480 or 800 by 600 and display at that size on a high-resolution screen.
  • Dead codecs and fonts. Old video formats play as black rectangles, and missing fonts reflow carefully laid-out screens.
  • Tracking that talks to nobody. Results went to a local file or an LMS (learning management system) that was retired long ago.

Test each piece on a spare machine, not your own. Write down exactly what happens. That log becomes the evidence for every decision that follows.

Why Can't Learners Open the Web-Packaged Versions Anymore?

Because the player they depend on has nowhere to live. Web-packaged Authorware played through the Authorware Web Player, a browser plugin. The packager split the piece into a small map file and a set of segment files, and the plugin streamed them down as the learner moved through the course.

Modern browsers dropped the old plugin architecture years ago, and the browsers that still supported it have been retired. So the files can sit on a perfectly healthy web server and still play nothing. The server is fine. The missing piece is on the learner's side, and you cannot ask hundreds of learners to install an unsupported plugin into a browser that will not accept it.

Could you keep one ancient browser in a virtual machine to view them? For an archivist, maybe, offline and off the network. For learners, no. An unpatched browser running an unpatched plugin is the kind of thing an IT security team is right to shut down.

What Are Your Options for an Old Authorware Library?

There are four, and they are not mutually exclusive. Pick per course, not per library.

OptionWhat it meansFits when
ContainKeep the original running on an isolated machine or virtual machine for reference onlyYou need to show what learners saw, but nobody new takes it
RetireArchive the files and records, stop offering the courseThe content is obsolete or covered elsewhere
ConvertBring the content into a modern tool, then clean it upThe content is still right and mostly linear
RebuildStart fresh, using the old piece as a referenceThe content is wrong, the logic is tangled, or the design aged badly

A simple rule helps. If a subject-matter expert would sign off on the content unchanged, lean toward convert. If they would rewrite more than half of it anyway, rebuild, because converting text you are about to throw away is paid busywork. The cost side of that choice deserves its own spreadsheet, and the math is laid out in the guide to whether you should rebuild or convert a legacy course.

Contain is the option people forget. It costs very little, and it settles the question auditors love to ask: what exactly did people see in that old module?

What Carries Over When You Convert Authorware Files, and What Doesn't?

Content carries over better than behaviour. That is the short version of every conversion of legacy Authorware files.

The parts that usually survive are the ones you can see: on-screen text, images, audio, video in a readable format, and the basic layout of each screen. Linear navigation (next, back, menu) maps across without much fuss. Simple interaction types, such as button choices, hot spots and text entry, often have a clear modern equivalent.

The parts that need a human are the ones you cannot see. Authorware courses kept a lot of logic in calculation icons and custom variables. Decision icons branched on conditions that were never written down anywhere else. Some pieces read and wrote external files, called custom code modules or relied on a specific Xtra. None of that converts by magic. Expect to rebuild branching, scoring and any tracking by hand, then test it against the original running in your contained copy.

Tools can take much of the grunt work off you. AuthorLearn Studio includes an importer that brings in legacy Authorware files you own, along with their assets and layout, and some files arrive up to 90% complete. It produces an import report listing what was approximated, and you review and finish the course yourself. That last step is not optional with any tool, and the import report is where you start.

Plan any move to convert Authorware to HTML5 as a two-stage job: import, then a scripted review against the original, screen by screen. The second stage is where the hours go.

Who Needs to Sign Off Before You Retire the Original?

More people than you would guess, and you want them before you delete anything. At minimum, check with these four:

  1. The content owner or subject-matter expert, who confirms the converted or rebuilt version teaches the same thing, or something better on purpose.
  2. Whoever owns training records, often compliance or HR. Old completion records may need to stay retrievable, and they may need to show which version of the course a person took.
  3. The LMS administrator, who knows whether historical records will survive when the old course entry is replaced.
  4. IT security, who will have opinions about that contained machine, and should.

Retention rules for training records vary by industry and country. That is a question for your legal counsel or records team, not for a course developer guessing. Your job is to make sure nothing gets thrown away before they answer.

Whatever they decide, archive the original package, the source files if you have them, a short screen recording of the course running, and your test log. Store them together. Future you will want all four in one place.

Authorware Courses Have a Second Life If You Plan the Move Before the Last PC Dies

Can you still run Authorware courses? Some of them, on the right machine, until that machine goes. The runtime is frozen, the web player has nowhere to run, and every Windows update is another roll of the dice.

The good news is that most of the value in those courses is content, and content moves. Test every piece on a spare machine, sort each one into contain, retire, convert or rebuild, and get your sign-offs lined up. Then move the courses while the old PC in the corner still boots. It is much easier to check a conversion against a working original than against somebody's memory of one.