I'm on Windows 10 with the recently installed creator update. Just checked and I am not experiencing a crash when adding resistors from the vault. Good luck with the issue.
Thanks for the response. It turns out I must have over done it when loading Altium Designer library files. I had to uninstall Circuit Studio completely and reinstall it for things to be working again.
I am also experiencing that issue. I was happy with CS now it’s crashing when I am in the Altium Vault. I am also having another issue with the Altium Content Vault. When I search for a part, in the vault explorer, I use to get a folder that was titled “All Folders” and the part I was searching for was inside that folder. I would click on the folder, it would open and the part list would appear. For some reason, this folder no longer appears when I do a part search in the vault explorer. Now what I get is a folder that reads, “ Object reference not set to an instance of an object”. I click on the fold, but nothing happens. It doesn’t open. Please see the attached screen shot. Are you experiencing the same issue?
Quite a few other people are experiencing this object reference error and it doesn't appear to be related to Windows 10 because I have it on my Windows 7 system. There are quite a few other posts on these forums about this issue.
Has anyone experienced this issue other than me? I recently got 'pushed' the Creators Update of Windows 10 and suddenly I get Blue Screens of Death whenever I try to pull a component out of the Altium Vault! (I'm only trying to place a generic 0805 resistor!) This has repeated itself twice. I was happily running Circuit Studio prior to this update, now I can't seem to use the Vault for anything.
Windows 10 Pro :
Win 10 Pro 64bit, v1703, Build 15063.138
AMD FX-8350, 16GB RAM
nVidia GeForce GTX 550 Ti, 1GB GDDR5
Altium Circuit Studio :
Ver. 1.4.0 (Build 84)
One thing to note, I am trying to create a simple voltage divider for a Simulation. (Maybe I shouldn't be using a component from the Vault for this? Could this be an Altium bug that just wasn't seen until this Windows update?)