Can't insert a user form

I get the error message that it cannot register the component. Most of the help on line says "the component can't be registered."

Then I went to my work machine and there is a Forms 2.0 Library. There isn't one on my home machine. Then I vaguely remembered something about a FM20.DLL that has to be browsed for and registered. I guess Microsoft wants to keep user forms a secret.

I found out that you have to search for FM20.DLL. I found it in SYSWOW64 and registered it and got the same error message. I also found it in C:/ ...root\vfs\SystemX86 and when I registered it, it cross-lined back to SYSWOW64 so failed again.

Is there another version of this DLL lurking out there, hidden somewhere? OR does anyone else have a solution for this "feature."

I posted in the Microsoft Community, but there haven't been any responses yet. Otherwise I'll call Microsoft this weekend and have one of their technicians fix it for me.

I have Windows 10 Home (64 Bit) and Office 365 (Home - 2016), 32 bit.

I'll just empathize with you. I hate tech glitches that can't be resolved with a little research. xl03 was much simpler and easy to work with.

Does any of the information or suggestions here help
https://social.msdn.microsoft.com/Fo...l?forum=isvvba

Thanks for the reference. It's 3 pages of different "solutions" and links to even more discussions. I've already wasted about 4 hours chasing rabbits down holes.

I'm going to give Microsoft a call this weekend and have them tell me how to fix it. One good thing about a 365 subscription is that you get technical support. I'll post back with what they come up with.

Well, this was a great disappointment.

I contacted technical support with a request for call back.

Chris called me back and after explaining the problem to him, he told me that I had to be forwarded to someone else.

So he forwarded me to a hold where I was eventually picked up by Mary (I think her accent was do bad I couldn't understand her). Who also couldn't help me, so she forwarded me to another hold queue, where I talked to John who could also not help me. So he forwarded me to another hold queue for commercial support where I held for 30 more minutes and eventually talked to Brandon who also was not an expert in this area.

However, Brandon stuck with me and called experts and tried to resolve the issue. My phone battery went dead after two and a half hours and he called me back on my alternate line. He was the bright spot in this affair. After 2.5 hours we gave up and he forward me to yet another department where I was told that I had to *PAY* to have the problem resolved.

I confirmed with the representative of this 5th department that I had to pay them to resolve a bug with their softwaer and they said, "Yes."

So bottom line - Microsoft does not support its 365 product.

Hi dflak

I had a similar issue a couple of weeks ago...Could not register FM20.DLL on a secondary pc...Windows 7 64bit, Office 2007 32bit
Perhaps it was just luck but how I solved was to deregister then delete the Microsoft Forms DLL Application.
I then took a copy off another pc re-registered and it worked perfectly...Not saying this could solve your problem...

Can you give me some more details. What do you mean by "deregister then Delete the Microsoft Forms DLL Application." What steps did you take.

Further investigation reveals that the issue is machine-related. I have 4 of my 5 Office licenses installed. My main machine has the issue but two of the three others don't. I haven't tried the 4th machine. All systems are on the April release of Windows 10.

FM20.dll is a standard dll that ships with Office so should be present on any machine that has Office installed with VBA support.

You haven't mentioned specifics of what you have attempted so far- have you attempted the full online repair of 365?

De-register
c:\Windows\syswow64>regsvr32 /u Fm20.dll
Then delete it from the Syswow64 folder
Then copied from another working machine to faulty machines Syswow64 folder and registered
c:\Windows\syswow64>regsvr32 Fm20.dll

run cmd as administrator

Hmm, I thought I had responded to this one.

Don: Yes I did run a complete online repair of office. Also the people at Microsoft tried installing various VBA programs. On my own, I copied over some DLLs from the good machines, put them in a "side" directory and attempted to register them. No matter what DLL I try to register, I get the same result. The Microsoft Forms 2.0 Library appears in the references, but I still cannot insert a form. The Forms 2.0 Library does not appear when next I launch Excel.

@sintek: Do you think I may have a problem? The machine with the issue is 64-bit. However, the Office installation is 32-bit. Is SYSWOW64 the correct place to go?

Yes for 64bit syswow64 is the folder...

Just for kicks register both 32 and 64

OK. I'll give this a shot when I get home tonight and see what happens. Thanks.

I attempted c:\Windows\syswow64>regsvr32 /u Fm20.dll and got the following message "c:\Windows\syswow64 is not recognized as an internal or external command operable program or batch file."

Hi dflak

My apologies...just to clarify...
Type cmd in search bar
When cmd.exe command comes up, right click and run as administrator...
The dos command prompt comes up as c:\Windows\system32>
This must first be changed....
Type cd c:\windows\syswow64
Now the dos prompt comes up with c:\Windows\syswow64>
Now you un-register...regsvr32 /u Fm20.dll
Follow same procedure as above to register and then type...regsvr32 Fm20.dll


My similar post same issues...xlnitwit got me through...
https://www.excelforum.com/excel-pro...a-error-2.html

Yeah, I know better. It wasn't all that late, but I was tired. I am not blaming it on the wine I'll try again tonight.

Good luck, hope you get it sorted....

Thanks for the help. However, it did not work out. I still get the same error.

I wonder what it is about this particular machine. It works everywhere else.

Perhaps check out the link in post 14 and try post 9 within that link...and try what xlnitwit suggested regarding .box and .exd files...

There should be .exd files (not .ext) in your temp folder if you are using the common controls, and there should also be an Excel.box file on your system. Are you including hidden files and folders in your search?

Originally Posted by sintek

Perhaps check out the link in post 14 and try post 9 within that link...and try what xlnitwit suggested regarding .box and .exd files...

There should be .exd files (not .ext) in your temp folder if you are using the common controls, and there should also be an Excel.box file on your system. Are you including hidden files and folders in your search?

I finally got around to trying this. I found only one .exd file: RefEdit.exd. I also found Excel.box. I deleted both of these and rebooted. It didn't help.

Fortunately, this is my home machine and I do not do a lot of development at home So I've been lazy at following up on the suggested links. I will report back when I conduct the tests. I did find out from the Microsoft Community that the correct DLL to use is the one in SYSWOW64.

OK, this is what did work. I was so close with sintek.

First I de-registered the DLL using regsvr32 /u FM20.DLL

Then I copied FM20.DLL and FM20ENU.DLL from a 32-bit system and pasted them into SYSWOW64.

Then I re-registerd using regsvr32 C:\Windows\SYSWOW64\FM20.DLL

Note no /i flag that everyone else (except sintek) said you were supposed to use. And for some reason, the full path name.

Anyway. It worked and it only took 7 months.

Well done...better late than never lol