File Share Encryption

Is there any known compatibility issues with SEE 10.4 and Intel Rapid Storage Tehnology? 

I am using an Asus H270 Systemboard. It is configured to use 2 Seagate Enterprise 1TB Hard Drives in a RAID1 configuration. I have loaded Windows 10 pro 64bit along with all the Windows updates. I then install SEE and encrypt the drive. After everything is finished and the system is finally moved to its final location, it boots to a 0xC0000001. I have tried for hours to get this unit up and working with no success(twice). 

The BSOD actually says: "A critical system driver cannot be found" and at the bottom:  "Page fault in non paged area" or something like that. Normally this would refer to a RAM issue so I have tested the RAM and found no problems. I have even taken the extra step to completely remove the RAM and install it in another system and it works fine. I even installed new RAM into the PC into a different slot. 

The second time I rebuilt the system I actually imaged it using the built in Windows 7 imaging app. Everything seems to have imaged properly and so off I went. After trying to reimage the machine it found the image on my external but once the restore was started I immediately was faced with a restore error.  So I guess my image is bad? Since then I have rebuilt the PC(third time) and created a backup image (2) before the encryption is done. Both backups are working and restore without issue.

So is there a compatibility issue?

Please help. This system is actually acting as a File Server and is supposed to be an upgrade to their previous server. Luckily their previous Server is back in place and working for them.

Thanks,

Howard

Update. The system worked great for 2 weeks. I installed a new controller and I thought I had this issue resolved. Apperantly not. The unit Blue Screened again and threw the exact same error.

I have taken the drives out to test and they both test ok.

Any thoughts.

what version of windows 10?  I have a very similar issue using 1709.  I'm curious if this is a compatability issue.

We are having this issue on almost every machine we attempt to update to Windows 10 version 1709.  It is causing us major headaches.  We end up having to boot off of the WinPE boot disc, decrypt the whole machine, and run a system restore to get it to work again, but we've even had some that come back with the same issue after resolving it.  Unencrypted machines have no issues running.  This only happens to machines on which we have PGP installed.  It's even happening on BRAND NEW machines coming straight out of the box and it's VERY consistent.  Symantec needs to get working on a fix for this.

We are having this issue on ALL of our new Dell Latitude 5580 Notebooks. Blue screen and STOP 0xC0000001.  The new machines are all Windows 10 1709.  No blue screen after the drive is decrypted.

Any word on this Symantec? My client would really like to have their new Server installed and working. Unfortunately, this has caused a major problem with regards to trust and system stability. They have opted to NOT install the new File Server until this issue is resolved. Please help.

The SED System requirements for the latest version (10.4.1) below, seem to suggest RAID is only supported for Server OS's:

http://www.symantec.com/docs/TECH236572

SEE does not support RAID at all:

http://www.symantec.com/docs/TECH104151

http://www.symantec.com/docs/TECH228432

http://www.symantec.com/docs/INFO3150

The last link is probably most relevant to you, as subscribing to it should give Symantec more evidence of it being a feature customers want, and therefore help them guide their development.

The first link is the most relevant as it has information from 2018. All other references are from 2015 and older.

The parts that I read that actually matter to me are:

and

• Symantec Encryption Desktop does not support operating system upgrades on encrypted systems through the Windows Update service

That last one kind of goes against the whole automatic update/upgrade process that M$ has implemented in Windows 10 so that needs to be changed. We can't be rebuilding machines that have just been given a windows update... especially since Microsoft doesn't/won't support machines that aren't 100% up to date. That means if you aren't receiving your regular MIcrosoft updates or that you aren't installing/implementing them, you are SOL. So it sounds like I have to choose between Microsoft or Symantec.. hmm.. hard choice..

and

• Boot drive must be partitioned in GPT with only one EFI system partition on the same physical disk
• Boot drive must not be configured with RAID or Logical Volume Managers (LVM)

I read that as though I need to install on a single non RAID disk and on a single partition. Seems that most drives or partitions I will be requiring encryption on will be RAIDed / high availability / large / high security drives. This seems to completely make moot any reason to get SEE in the first place. I feel this corporation will be moving on to a different vendor.. unless I have missread something.

It's unfortunate. Our old Windows 7 Pro machine running RAID 1 handled SEE quite well. Sad to see we have to change things up because some companies can't / won't keep up with the curve. 

Thanks for the info. 

Deleted duplicate.

Like you say, it sounds as if you are at a bit of an impasse now.  Neither SED nor SEE support RAID, so it's possible that while it previously worked for you, that you were always using it in an unsupported configuration anyway.

Regarding the inplace upgrades for Win10 though, I'd suggest you review the below article (though even then, I'd recommend contacting Symantec Support to get confirmation of the scripts working for 1709):

http://www.symantec.com/docs/HOWTO125876