Unable to edit blocks

[Anonymous]

Hey guys I've run into an interesting problem here...

I just switched computers with someone else in my office and had to re-download AutoCAD 2020. All of my files were transferred over along with all my existing settings on my previous computer. When I got back into the program I was unable to edit my blocks. I've tried opening some old drawings and it's the same issue with every file.

I've tried editing my double click function for blocks to open the block editor, which is the way I always access it. This didn't work.

I also tried to use different commands such as "BEDIT", ".BEDIT", and "._BEDIT". None of these commands worked either.

Also, my "BLOCKEDITLOCK" is already set to "0" at the moment.

Before I switched computers I updated to the latest version... even with the latest version I noticed a few other small differences even though I'm up to date still. My lineweight displays looks a little different and some of the color settings are different in my model space. Other than that everything seems to be the same.

Has anyone run into an issue similar to this or already have a possible solution to this problem?

Any help is greatly appreciated!

-Josiah

[pendean]

What does "didn't work" mean to the rest of us? Usually there is an error message at the commandline, you might have to make it taller than a single line to see it.

[Anonymous]

I keep getting "Unknown command "-BEDIT". Press F1 for help."

[GrantsPirate]

Clarification needed.  You type the command -BEDIT and the program says unknown command, or you enter a block name and nothing happens and or an error message appears?

Try selecting a block that is inserted in the drawing, right click and pick Block Editor or Edit Block in Place.  What happens?  Error message, absolutely nothing, etc?

[Anonymous]

Here's what I copy and pasted:

Command: _-bedit
c:\program files\autodesk\autocad 2020\acauthenviron.arx cannot find a procedure that it needs.
Unknown command "-BEDIT". Press F1 for help.

[GrantsPirate]

You may not have all the paths in Support File Search Path (in options).  Compare to a machine that works.

Also try making sure DEMANDLOAD is set to 3.

[Anonymous]

Unfortunately  I don't have another machine to compare to...

[Alfred.NESWADBA]

Hi,

try first to reset settings to default as described >>>here<<<.

If that does not work run a repair installation (>>>details<<<).

- alfred -

[pendean]

Always add a period as part of the name when something like this happens, that always calls a core command no matter what:

.BEDIT
or
-.BEDIT
or
.-BEDIT

If any of the above work, you have an add-on that killed the command in normal operation for you, or you have an exceptionally bad installation at play.