by Kevin Siegel 
Over the past few weeks I've gotten several emails from Captivate developers using Windows 10 and Captivate 9 who get the following error when attempting to record software simulations:
A quick Google search found the following forum article. According to the post, you need to edit the AdobeCaptivate.ini file found within Captivate's application folder.
While I'm using Windows 10 and have not run across this issue, I'm teaching Adobe Captivate at ATD's TechKnowledge this week and wouldn't you know it, one of my students (Brian O'Neill) got hit with the error message above. Unfortunately, my student wasn't able to edit his INI file.
Brian didn't give up. He was able to fix the problem and shares his steps below.
When I attempted to modify the AdobeCaptivate.ini file I received an "access denied" message. It appears that Captivate sets some restricted permissions in the /Program Files/Adobe/Adobe Captivate 9 x64 folder.
My workaround was to right-click that folder in File Explorer and choose Properties > Security > Users. On the Security tab, I enabled "Full Control" for Users and clicked OK.
My workaround was to right-click that folder in File Explorer and choose Properties > Security > Users. On the Security tab, I enabled "Full Control" for Users and clicked OK.
I was then able to open and edit the AdobeCaptivate.ini file in Notepad and change the listing for DpiAwareness from 0 to 1. Captivate now appears to operate normally.
***
Looking for training or help with Adobe Captivate? Check out these awesome live, online Captivate classes.
After I wrote the article above, I received the following helpful information from fellow Captivate developer Lieve Weymeis:
Kevin, in the article about changing INI file for Win10, some very important info is missing:
1. You have to do this only for retina screens, not for normal screens and just to capture such a retina screen
2. When finishing the capture you have to restore the old INI file or you will have issues with Captivate being too small to read on the retina screen.
I always keep both INI files on the desktop to switch easily.
Posted by: Kevin Siegel | January 19, 2016 at 09:58 AM
I think it is Windows that disallowed editing the ini file in the Program Files folder. I hit this with something else and the workaround I used was to copy the file to another location, edit it and then copy it back. Windows does allow that!
Posted by: Peter Grainge | January 20, 2016 at 04:27 AM
Peter's workaround worked for me as I was unable to even change the access levels in the folder properties.
Posted by: Abigail | July 19, 2016 at 05:38 PM