Author Topic: Update to 6.7.1 left quite a few of our computers nonbootable.  (Read 791 times)

Offline Frank Summers

  • Newbie
  • *
  • Posts: 1
  • Kudos +0/-0
There was the same issue in an earlier version. We had to boot with a windows usb disk. Deleted C:\windows\system32\drivers\saappctl.sys. Restarted, computers booted into Windows.

Offline Massimo Iannilli

  • Newbie
  • *
  • Posts: 1
  • Kudos +0/-0
Re: Update to 6.7.1 left quite a few of our computers nonbootable.
« Reply #1 on: March 10, 2022, 09:35:11 PM »
Thank you for your suggestion, i will try it late. I had two Windows Server blocked (2019 e 2012) ... my notebook is working without problem

Offline Mitch Hicks

  • Newbie
  • *
  • Posts: 2
  • Kudos +0/-0
Re: Update to 6.7.1 left quite a few of our computers nonbootable.
« Reply #2 on: March 15, 2022, 12:12:53 AM »
There was the same issue in an earlier version. We had to boot with a windows usb disk. Deleted C:\windows\system32\drivers\saappctl.sys. Restarted, computers booted into Windows.

seems to be KB5011487 and 6.7.1...
removing the file didn't work for me... so far the only solution is full system restore from backups...
i have 2 more computers out of 8 any suggestions before i have to wipe?

Offline Mitch Hicks

  • Newbie
  • *
  • Posts: 2
  • Kudos +0/-0
Re: Update to 6.7.1 left quite a few of our computers nonbootable.
« Reply #3 on: March 15, 2022, 01:42:04 AM »
so tried again...Deleted C:\windows\system32\drivers\saappctl.sys and the C:\Program Files\SecureAge
the computer booted and i was able to install windows updates...

I will update after trying to reinstall...

Well Can't install 6.7.1 computers won't boot...

« Last Edit: March 15, 2022, 03:41:00 AM by Mitch Hicks »

Offline hendy

  • SecureAPlus Developer
  • Sr. Member
  • *****
  • Posts: 345
  • Kudos +16/-0
Re: Update to 6.7.1 left quite a few of our computers nonbootable.
« Reply #4 on: March 17, 2022, 08:11:26 PM »
While we are investigating the issue, temporarily we have reverted the download version to 6.7.0.
We apologize for the inconvenience caused.

To fix the issue, you may refer to:
https://secureaplusforum.secureage.com/index.php/topic,347.msg987.html#msg987