Access – The wizard you’ve requested is not installed or is in a bad state.

Here’s a new one for me. I was at a client’s simply trying to use the Linked Table Manager and received the following error message?!

The Wizard you’ve requested is not installed or is in a bad state. Please install or reinstall the wizard. If you do not have permissions to do this on your computer see your system Administrator.

Of course, the standard troubleshooting was performed

Reboot
Repair
Uninstall/Reinstall

Sadly, nothing worked. And then I Googled and came across a thread on dbforums entitled Wizards not working in Access 2013 in which I learnt that Microsoft, in certain cases, appears to not configure the Trusted Locations to include the ACCWIZ folder and thus we get the error whenever we try and launch any of the wizards. That’s right, Microsoft improperly sets up the Trusted Locations for the ACCWIZ folder.

Luckily for us, it is an easy to fix!

If you open the Trusted Location Editor

File -> Options -> Trust Center -> Trust Center Settings -> Trusted locations

You’ll be able to see in the listing of existing Trusted Locations an entry for …\…\ACCWIZ\ and if you check, I’ll bet you that you will not find such a folder in that location. Thus the issue.

On the PC I was working on it listed

C:\Program Files (x86)\Microsoft Office\Office16\ACCWIZ

as the location, when in fact, on the PC I was using, it was located in

C:\Program Files (x86)\Microsoft Office\root\Office16\ACCWIZ

but that doesn’t mean it will be that same location for you. You can simply use Windows Explorer to perform a search for the folder by simply entering foldername:ACCWIZ in the search box and then right-click on one of the returned files and select Open file location to see the full path to the proper folder for your setup.

The solution, simple as it is, is to click the Add new location button and go and locate the proper location of the ACCWIZ folder on your PC, click OK and you’re done! Just close the remain dialog(s).

Note

This issue relates to Access 2013 and 2016 and is not the same as what occurred in Access 2010 with the same message! If you are experiencing this issue with Access 2010 I’d suggest you look at

8 responses on “Access – The wizard you’ve requested is not installed or is in a bad state.”

erwin leyes November 7, 2017 at 8:15 pm

I’ll just wait and see Access 2019, for the mean time i’ll just hang on A2010. I think next to A2003, A2010 is the most stable version. By the way sir Daniel any idea of the next version of AWA? thanks and good day to you.

Daniel Pineault Post authorNovember 7, 2017 at 8:27 pm

They are trying to replace AWAs with PowerApps. Sadly for Access developers, PowerApps are a far cry from what we are used to. IMHO, I highly doubt, after 3 failed attempts to webify Access that the Access Dev Team will be attempting anything again in the near future.

My advice, which it has been since the beginning, is if you need a web application, then turn to a proper web technology, PHP, .NET, … With the way Microsoft has repeatedly dropped the ball on Access, even if they came out with a new “solution” for the web, I would run the other way!

erwin leyes November 8, 2017 at 12:31 am

Access is probably the most flexible and productive database front end on the planet. I wonder why in spite of so many web frameworks out there none was able to match Access power as a RAD db fe tool. The only web devt tool that emulate Access was morfik, but sadly it’s development was stop.

Rick Stephens March 5, 2019 at 8:16 pm

Well done Daniel. Worked a treat! Although in my case it was :-
C:\Program Files\Microsoft Office 15\root\office15\ACCWIZ\

Never too sure about whether I should look in C:\Program Files\ Or :\Program Files (x86)\

Thanks anyway.

Daniel Pineault Post authorMarch 6, 2019 at 6:02 am

C:\Program Files (x86)\ -> 32-bit applications
C:\Program Files\ -> 64-bit applications

I know just one more level of confusion.

Rick Stephens March 5, 2019 at 8:38 pm

Further to my last message.
What the hell is Microsoft doing ? This used to be okay and I have no idea when this was changed. Are these updates occurring in MS Defender updates ? which is the only way I can think that this change could have occurred.

Daniel Pineault Post authorMarch 6, 2019 at 6:05 am

I suspect a Windows or Office update wrecking havoc which is now the norm it would seem.

John Litchfield November 12, 2020 at 11:02 pm

Here is my remark which I think will be helpful to people:

Here is another cause of that wizard error:
I found out that this error message can occur if the usysreginfo table has incorrect data specified in the Expression property/record. For example, the error occurred for me because I had a sub procedure specified there instead of a function. It must be a public function.

Hoping this will help someone.

Another obvious cause is the path is wrong for the addin. Maybe that might be worth adding as well, but nonetheless something a little easier to guess…

erwin leyes November 7, 2017 at 8:15 pm

I’ll just wait and see Access 2019, for the mean time i’ll just hang on A2010. I think next to A2003, A2010 is the most stable version. By the way sir Daniel any idea of the next version of AWA? thanks and good day to you.
1. Daniel Pineault Post authorNovember 7, 2017 at 8:27 pm
  
  They are trying to replace AWAs with PowerApps. Sadly for Access developers, PowerApps are a far cry from what we are used to. IMHO, I highly doubt, after 3 failed attempts to webify Access that the Access Dev Team will be attempting anything again in the near future.
  
  My advice, which it has been since the beginning, is if you need a web application, then turn to a proper web technology, PHP, .NET, … With the way Microsoft has repeatedly dropped the ball on Access, even if they came out with a new “solution” for the web, I would run the other way!
erwin leyes November 8, 2017 at 12:31 am

Access is probably the most flexible and productive database front end on the planet. I wonder why in spite of so many web frameworks out there none was able to match Access power as a RAD db fe tool. The only web devt tool that emulate Access was morfik, but sadly it’s development was stop.
Rick Stephens March 5, 2019 at 8:16 pm

Well done Daniel. Worked a treat! Although in my case it was :-
C:\Program Files\Microsoft Office 15\root\office15\ACCWIZ\

Never too sure about whether I should look in C:\Program Files\ Or :\Program Files (x86)\

Thanks anyway.
1. Daniel Pineault Post authorMarch 6, 2019 at 6:02 am
  
  C:\Program Files (x86)\ -> 32-bit applications
  C:\Program Files\ -> 64-bit applications
  
  I know just one more level of confusion.
Rick Stephens March 5, 2019 at 8:38 pm

Further to my last message.
What the hell is Microsoft doing ? This used to be okay and I have no idea when this was changed. Are these updates occurring in MS Defender updates ? which is the only way I can think that this change could have occurred.
1. Daniel Pineault Post authorMarch 6, 2019 at 6:05 am
  
  I suspect a Windows or Office update wrecking havoc which is now the norm it would seem.
John Litchfield November 12, 2020 at 11:02 pm

Here is my remark which I think will be helpful to people:

Here is another cause of that wizard error:
I found out that this error message can occur if the usysreginfo table has incorrect data specified in the Expression property/record. For example, the error occurred for me because I had a sub procedure specified there instead of a function. It must be a public function.

Hoping this will help someone.

Another obvious cause is the path is wrong for the addin. Maybe that might be worth adding as well, but nonetheless something a little easier to guess…