Skip to main content
4-Participant
December 10, 2025
Solved

Creo 11 saves unchanged Components when saving only one assembly

  • December 10, 2025
  • 1 reply
  • 239 views

We switched to Creo Parametric 11.0.5.0 on Monday.

Now we’ve noticed that when we save an assembly that hasn’t been modified, all the contained parts and assemblies that are in an older Creo version are also being saved. In one example, 160 out of 211 Creo files were saved. The config.pro save option is set to save_objects changed_and_specified. Even save_objects changed has no effect.

The problem is that our document management tool “Workspaces Desktop” from the company Contact interprets this as a change and now considers all these documents as modified, wanting to save them or even re-index documents that have already been released. That would be disastrous.

Has there been an adjustment on PTC’s side? This behavior was definitely different in Creo 9 and previous versions! It’s not related to versioning. That option should remain active.

This is about saving files that have not been changed. We just tested again with Creo 9 using a different assembly. Same procedure: once with Creo 9, once with Creo 11—different result. Many more files are being changed. There were even Creo files from version 7 included. These were not changed by Creo 9, but they were changed by Creo 11.
PTC Artikel: CS409743

Best answer by MartinHanak

Hi,

Creo 10.0.5.0, Creo 11.0.1.0 and Creo 12.0.0.0 will stop modifying old files using the hidden config.pro:

prevent_silent_sync yes/no*

 

hidden means that you have to add prevent_silent_sync YES to config.pro manually in Notepad and restart Creo.

1 reply

4-Participant
December 10, 2025

PTC Artikel: CS409743

24-Ruby III
December 10, 2025

Hi,

Creo 10.0.5.0, Creo 11.0.1.0 and Creo 12.0.0.0 will stop modifying old files using the hidden config.pro:

prevent_silent_sync yes/no*

 

hidden means that you have to add prevent_silent_sync YES to config.pro manually in Notepad and restart Creo.

4-Participant
December 11, 2025

Hello Martin.

 

Thank you very much for your suggestion! Setting the config.pro option prevent_silent_sync to YES has achieved the desired result!