Back after my little 3 Day ban :) :)

Not a windows issue! It was a known issue at smith micro caused by the activation method ( Call Home ) in poser 11++ that had cycle renewing. crashes that were caused from hierarchal changes either in the hierarchy editor or in the setup room some in the material room, even if a change got pulled with no intentions could cause poser to crash in a heavy way blowing off the Licence in the activation folder, also other personal settings could of gotten affected after such a crash up to a big kill that poser could not be started again.

SM fixed the issue by activating a permanent Licence in poser what actually prevented such heavy crashes in the setups.

assuming that this fix got removed when bondware made a roll back on the activation system of poser setting it to renewing Licence.

you can find the issue in the Poser log file if you want to figure out how much damage your crash caused sending it to bondware. I just do not recall where that Logfile is :( :( :( been quiet a while since i used it last. but bondware might be able telling you where it is located.