VLISP internal error

[Anonymous]

Since a week or so every time I start AutoCAD 2018 a message pops up saying that there is a 'VLISP internal error' (unhandled execption on init) . In the loading sequence it seems that when AutoCAD is trying to load the vl.crx.

It will asked to send info to Autodesk, which I did, but i'm not expecting much of that. The software gives me a choice to stop or continue. when I continue it seems to work properly, but I'm not sure since I'm not touching every feature there is. 

I did a complete uninstall according AutoDesk rules and reinstalled. With no result. I installed AutoCAD 2016 which gave the same error already during installation. 

Installing AutoCAD 2019 for testing purposes also gave the same message after starting the software. 

I suspecting the Windows 10 October update but cannot prove it. That is the only major change on my machine. AutoCAD 2018 is running just fine for at least half a year or so. 

Any idea anyone?

[john.vellek]

Hi @Anonymous,

I have seen another case like this.  It does appear to be related to a Windows update.  I believe that something such as a security patch might be blocking this Visual Lisp from loading.  A future KB from Microsoft should remedy this problem.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[cfagerst]

I have exactly the same problem. Same message popup when trying to load vl.crx. Also get the option to continue and seems to work, but can't give a machine to a customer in this state. This happens on 3 similar brand new machines (Dell Precision 3630) with a fresh install of Win10 1809 (October update) downloaded from Microsoft before they pulled it.

Before deciding whether to go with 1809 instead of 1803 on these new machines, I tested it on several existing machines on which I upgraded W10 to 1809 manually.

Strangely enough, on all these three test machines, one Dell Precision M 7510 laptop, one Dell Latitude 5480 laptop and one custom built intel 7th gen desktop, Acad works flawlessly with 1809. They were upgraded from 1511, 1607 and 1803.

From what I've been reading some other people haven't been as lucky with the 1809 upgrade though. If i'ts a Microsoft problem, is there any time frame for the possible KB fix that will address this issue?

I'm not very keen on reinstalling the machines with 1803 at this point, and I'm also worried that Microsoft will soon re-release this 1809 update and start pushing it on all machines with win update enabled (Which we have here for some technical reasons) ,and possibly brick some actual users Autocads, which apparently was what happened to the OP Mr. Uiterwijk...

Any help, news or ideas around this subject would be appreciated.

[john.vellek]

Hi @cfagerst,

I just did a little searching on the web and there is still no re-release date for the October Windows 10 update. I am hoping that it is delivered shortly and will fix some of the issues created in the initial release.

[john.vellek]

Hi @cfagerst & @Anonymous,

If you could provide a NFO for me that might help the team isolate the exact reason you are seeing this.

If your data needs to be private or confidential, please email it directly to me at john.vellek@autodesk.com and please include a link to this thread in your email.

[cfagerst]

Hello John,

Attaching a .nfo file or a .7z of the file here didn't work, so i emailed it to you as instructed.

Br, Christoffer Fagerström

[cfagerst]

Status update: I joined the windows insider program on one machine to test if new updates would solve the issue. I got the KB4464455 update that updated Windows 10 to OS build 17763.104.

Unfortunately this didn't solve the issue though...

[cfagerst]

I managed to solve the issue.

The solution was changing windows regional settings from "Match windows display language" (Windows is in english, and this was the default out of the box setting) to Finnish(Finland) and the decimal symbol from , to .

For the OP (Dutch?) the resolution would be similar I guess? Something to do with different language standards displaying some symbols in a different way and ACAD code not liking it.

Kind of an easy fix, but really hard to find...

[john.vellek]

Hi @cfagerst,

I am glad this worked on your side.  I am still having problems duplicating this on my side however and was hoping you could confirm the attached screen images as to what you did.

I appreciate your help on this issue!

Please select the Accept as Solution button if my post solves your issue or answers your question.

[cfagerst]

Hello again,

Maybe I was a bit unclear in my last post. I'm not at work until Monday so can't verify the exact settings, but I would guess the point is to have the same setting in both the "Location" tab as int the "Formats" tab. My problem was that Location was Finland and Formats were "Match display language" (English). So depending on where you are these two tabs should point to the same country/region.

My guess is that Autocad looks at the "Location" value and expects that kind of symbol standards, so having a different country/region in "Formats" would most likely mess things up, like it did in in my case.

For the OP (Original poster), whom I would guess being from the Netherlands looking at the name, the correct setting would be Netherlands/Dutch. 

Hope this helps.

Br, Christoffer Fagerström from Finland.

[john.vellek · Accepted solution]

Hi @cfagerst & @Anonymous,

The team found in their investigation of this issue that there is a Region Settings in Windows that seems to cause this issue. If you go into the Region control panel and select Change System locale, the Region Settings window displays Beta:Use Unicode UTF-8 for worldwide language support. Unchecking this option should correct the behavior.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[Anonymous]

Hi,

I have the exact same problem and the problem occured after I upgraded to 1809 (from 1803).

Unfortunately the recommendations here did not solve the problem for me. 

My computer is a brand new Dell Precision 3530 with Windows 10 Pro version 1809. I had to upgrade to 1803 because the Windows start menu disappeared. So I do not want to downgrade.

Do anyone have som more suggestions?

Best Regards,

Karl-Ebbe

[Anonymous]

Hi again,

Some additional information; When I mark the box; "Beta: Use Unicode UTF-8 for worldwide language support", then AutoCAD start but show errormessage during startup, telling that there are problems loading visual lisp. But after a few minutes AutoCAD shows "Unhandled Exception" and crashes. 

When i remove the mark in the box; "Beta: Use Unicode UTF-8 for worldwide language support", then AutoCAD "hang" during startup and I never come to the editor.

Best Regards,

Karl-Ebbe

[cfagerst]

Hello,

Did you try the region and language settings suggested by me earlier in this thread? (Match display language -> The language of your keyboard, if different than your display language). That worked for me at least. Changing decimal symbol could also help. The problem in ACAD would most likely be some symbol in the code being different than expected (eg. ; instead of : or , instead of .)

[Anonymous]

Hello,

Thanks for your answer!

Yes, I have tried but probably in some wrong combination. 

Now I have made sure that there are same in "Location" and "Format" tabs. Strange enough I have the decimal to "," as defined by the Swedish language setting. 

But now it works 🙂

Thanks a lot!

[L5367]

What worked for me, I just changed my default

 

to

Did not need to change the decimal symbol from additional settings. (tested both)

[Anonymous]

Hi,

Thanks for your answer!

Yes, it was (finaly) what worked for me as well.

[Anonymous]

I've changed my Regional format under Region from Dutch to English (United Kingdom), and then the problem was gone. As others have mentioned I also suspect the decimal separator as the cause, in dutch this is the comma instead of the dot.

If this is the problem, then roughly half the world should be having this problem and I'm surprised that AutoDesk hasn't caught this.

[Anonymous]

oh finally, so meny hours wasted to figure out the problem. Finally got it to work to changing format from english to finnish.  this link https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/VLISP-...

did not help me at all bcs didnt solve the problem. Just chanhing the format solved it.

[Anonymous]

My regional format was Sweden when I changed to united state it is work

---

@Anonymous wrote:

Since a week or so every time I start AutoCAD 2018 a message pops up saying that there is a 'VLISP internal error' (unhandled execption on init) . In the loading sequence it seems that when AutoCAD is trying to load the vl.crx.

It will asked to send info to Autodesk, which I did, but i'm not expecting much of that. The software gives me a choice to stop or continue. when I continue it seems to work properly, but I'm not sure since I'm not touching every feature there is. 

I did a complete uninstall according AutoDesk rules and reinstalled. With no result. I installed AutoCAD 2016 which gave the same error already during installation. 

Installing AutoCAD 2019 for testing purposes also gave the same message after starting the software. 

I suspecting the Windows 10 October update but cannot prove it. That is the only major change on my machine. AutoCAD 2018 is running just fine for at least half a year or so. 

Any idea anyone?

---