Microsoft Surface Pro 7 users have reported a frustrating bug that causes the 2-in-1 laptop to shut down erratically.

According to Notebookcheck (via Laptop Mag), angry Microsoft Surface Pro 7 owners joined the manufacturer's community forum website in December to get guidance on the erratic shutdowns. As of this month, these shutdowns are still being noted, with over 500 users expressing that they are experiencing the same issue.

According to responses from Microsoft employees on the forum, the erratic shutdowns, which appear to affect all Surface Pro 7 models, are being "actively" investigated.

Another Microsoft representative shared workaround steps to change the Surface Pro 7's default sleep time. While it appeared to be a potential fix, users are still experiencing problems with their devices as of this week.

In fact, the random shutdown threads continue to grow, reaching 29 pages as of the latest report today (April 17).

"If the device stays ideal for a minute, it shuts down directly," one user wrote."

"I checked all sleep and power settings and everything is fine.

Does this sound like the problem you are experiencing? While there is no universal solution (yet), here are some things you can try when faced with random shutdowns of the Surface Pro 7.

Shortly after the Surface Pro 7 random shutdown thread began, a Microsoft agent suggested that users press and hold the power button for at least five seconds when the shutdown occurred.

If that did not resolve the issue, the representative suggested running Windows Update and using the Surface Diagnostic Toolkit. Then check the reliability history of the Surface Pro 7 and contact customer support with a screenshot of the report to see if another bug could be causing the random shutdowns.

Another potential solution is to change the device's power and sleep settings. Switching the default from 5 minutes to 1 hour may work.

If you have tried these workarounds and are still suffering from random shutdowns on the Surface Pro 7, you are not alone. Clearly, there is a much larger problem at hand that Microsoft needs to rise up and solve.