Hey everyone, just looking to see if anyone is experiencing similar problems with self-hosting Sisense on a AWS instance. First, here's some background info on our setup:

• Windows server 2016 datacenter
• 4 cores, 2.30GHz processing (x64 processor)
• 32GB ram
• 200GB disk space (less than 50% used)
• Sisense v8.0.1 (however, this issue has occured on every version we installed with 7.0)

And here's what's happening... whenever there's a windows cumulative update available and sisense services are running, the CPU will skyrocket making the server barely usable until we stop all sisense services (this lowers CPU and makes it more usable), install the update, restart the comp, then start sisense services again. This server is also relatively clean and only used for sisense software. 

We had auto-updates turned on but eventually disabled them because even having an update in queue would raise CPU and make the server crawl. Now they're turned off but we're still experiencing issues when a cumulative update is available. I've started working with IT and they think they can create a script that with stop sisense services, install available updates, restart the server, then start services again - but this seems like a lot of work for something that shouldn't be happening in the first place.

Does anyone here experience similar issues or have any ideas on what could be happening? I appreciate any feedback!