Weldment - Invalid Path?

[m2shell]

This problem just appeared out of nowhere.
When I go to insert a weldment feature, I get an error "Invalid Path".
My Weldment Profile path is set correctly in File Locations
But it looks like it is trying to access a location called "\\\C:\Program Files\SolidWorks Corp\...(etc)"

Why would it be looking in such a strange location?

I even checked the file location in registry, but it looks fine.

Off subscription so can't try VAR.

Already tried a repair. Should i just re-install?

SW2022sp5

[AlexLachance]

I know you looked in the registry but try a Registry reset:
https://www.javelin-tech.com/blog/2019/ ... -registry/

[m2shell]

I know you looked in the registry but try a Registry reset:
https://www.javelin-tech.com/blog/2019/ ... -registry/

Good idea.

I tried, and I was able to insert Weldment without an error.
THEN
I restored my customizations via the "Restore Settings" command. And the error re-appeared.
I then Re-Restored to an older setting backup and the problem went away.
So it looks like I have some corruption in the most recent customization backup.... wow

[Frederick_Law]

Don't restore everything.
Uncheck and only restore one category.
See which one cause problem.

[m2shell]

Don't restore everything.
Uncheck and only restore one category.
See which one cause problem.

Yep. It was the System Options settings that were causing the problem.

Thanks!

[Frederick_Law]

Now, compare the setting files and see what's different.

Notepad++ can do that with Plugin:
https://notepad-plus-plus.org/downloads/

[mp3-250]

solidworks has the bad habit to export sldreg as an invalid registry file to begin with... I had a very bad experience deploying system options with a sldreg. solidworks FIXES the sldreg after some consistency check but exports garbage like SOME paths without escaping the slashes resulting in invalid paths...

[m2shell]

solidworks has the bad habit to export sldreg as an invalid registry file to begin with... I had a very bad experience deploying system options with a sldreg. solidworks FIXES the sldreg after some consistency check but exports garbage like SOME paths without escaping the slashes resulting in invalid paths...

I haven't yet done the comparison with Notepad++ that @Frederick_Law recommended. But I think it all started last week when I was creating some new macro buttons and experienced some "irregularities" during the process...

Now that I think of It has SW yet fixed the behavior that you can't delete a macro in the "Keyboard Shortcut" menu once you've put it there? I still have some bespoke macros defined there from 6-7 years ago that have no context anymore.

[Frederick_Law]

solidworks has the bad habit to export sldreg as an invalid registry file to begin with... I had a very bad experience deploying system options with a sldreg. solidworks FIXES the sldreg after some consistency check but exports garbage like SOME paths without escaping the slashes resulting in invalid paths...

Do not export on first start of SW after install.
SW won't write to registry until it close.
That export will be mostly empty.

[m2shell]

Do not export on first start of SW after install.
SW won't write to registry until it close.
That export will be mostly empty.

Wow. That's a great bit of info. Thanks @Frederick_Law

[mp3-250]

Wow. That's a great bit of info. Thanks @Frederick_Law

This is a nice finding and I will keep it in mind.thank you for sharing @Frederick_Law
Unfortuanatelly I had a bad experience well after the first startup, in fact I imported and exported again the SLDREG file "to clean it up" with SW checks and be sure I was using a proper registry file before deploying to our clients.
Solidworks fails to write a proper REG4 format and implodes if you apply that registry file outside Solidworks.

I was wrong.
see viewtopic.php?t=2586

Imagine a *working* administrative tool that allow you to setup *all* options inside SW, PDM, EDRAWINGS, SIMULATION inside a coherent envroinment...