Skip to main content
7-Bedrock
February 3, 2026
Solved

Parametric Crashing when sending email

  • February 3, 2026
  • 3 replies
  • 173 views

We have an issue with a single user that is unable to send email from within Parametric 10.0.9.0. It will save as and generate files without issue but will just close out of the program entirely when it would usually be opening Outlook. It does this with all file types. Event viewer shows xtop.exe crashing but not much in the way of info. Other users can send without issue. Outlook has been repaired and stripped of add-ins to test. It is functioning fine.

Best answer by dlitchfield

We found the issue. Microsoft pushed out an update to 365 that broke this in the 10.0.9.0 and 10.0.10.0 versions that we know of. Our vendor was able to duplicate the problem in a 9 and 11 version as well. The fix was to switch over to the enterprise update channel on a new install of Office that did not have the update. This only updates twice a year instead of whenever Microsoft feels like it.  

3 replies

Catalina
Community Moderator
February 10, 2026

Hi @dlitchfield 

Thank you for your post. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

 

Best regards,

Catalina | PTC Community Moderator
12-Amethyst
February 11, 2026

I don't have much to offer but simplicity's that you probably have done already. But from my experience in similar I have:

  1. Made sure all my computer updates are 100% (firmware, software, etc.). 
  2. Use zip
  3. Are there any custom options or configs that show any possible interference - compared to a successful user all setups and options?
  4. If all fails, send email separately from Creo. Hence, save file outside Creo, zip it, send it. 
  5. Good luck.

All in all, seems like isolated, and if the user has luck like me then there are gremlins in their computer. Try using a different computer with same user and the user's setup. On a couple of my issues that stood alone from all other successful users, that it was my computer. So, they swapped it out for another, rebuilt my stuff into the replacement computer, and all was good. Although, my issues differed than yours. 

dlitchfield7-BedrockAuthorAnswer
7-Bedrock
February 24, 2026

We found the issue. Microsoft pushed out an update to 365 that broke this in the 10.0.9.0 and 10.0.10.0 versions that we know of. Our vendor was able to duplicate the problem in a 9 and 11 version as well. The fix was to switch over to the enterprise update channel on a new install of Office that did not have the update. This only updates twice a year instead of whenever Microsoft feels like it.