On HP 800 G3 Elitedesk PC with Windows 10 Enterprise build 1709 or 1803 with Virtualization enabled in the BIOS Windows will not boot after installing Adobe Photoshop Elements 2018 or Adobe Premier Elements 2018. It boots to a blue screen that states "Your PC did not start correctly" with an error code of 0x0000001.
The only way we can get the workstation to boot into Windows after installing either of these products is to disable the Virtualization in the BIOS. But then Credential Guard does not work and that is one of our security requirements. I have done the Adobe installs with no antivirus installed just to eliminate that issue. I have also updated the video driver directly from Intel rather than from HP as suggested in another forum. Nothing has worked yet. We need a solution to be able to use Credential Guard with these Adobe products or we may have to find alternative products to use that will work with Virtualization enabled in the BIOS.
We are having the same issue with Windows 10 Enterprise Build 1803 and our HP EliteBook 840 G5 laptops.
It is strange as it does not seem to affect other models (e.g. HP EliteBook 840 G3 / G4) but my understanding is the VTx technology is used throughout these.
Please could it be advised what could be causing this and if there is anything that can be completed to prevent the requirement to turn off this setting, or as above we will also need to look at other solution away from Adobe products.
We have done a lot more testing and have discovered that the issue is due to Credential Guard. When we install Windows from dvd and have virtualization on in the BIOS, we have no problem with these Adobe products. When we turn Credential Guard on with the local group policy we wind up with a non-bootable Windows 10 workstation. We turn Credential Guard off and reboot twice and we are able to boot into Windows again. I have a support ticket open with Microsoft for this issue, but they have not been helpful at all with this issue.
Thank you for coming back so quickly. Did you only have to disable credential guard or the whole of Virtualisation-based security?
Did you complete this via GPO or locally on each of the problem machines? It would seem that if this has been enabled by GPO and UEFI lock was enabled, it is not possible to turn this off remotely and requires a touch of the machine, so it would be good to know how you got around the issue.
We turned off virtualuzation in the BIOS to get a few machines deployed quickly.
Going forward we will most likely break out the Credential Guard settings from our security baseline policy and make a new policy just for Credentail Guard. We would deny the group policy access to workstations that have these Adobe products. Much easier than having to set the BIOS settings differently and possibly having to physically visit those workstations later if a resolution is found.
we will also need to look at other solution away from Adobe products.
Be advised that this is a user-to-user forum, not Adobe corporate. A functionary for Adobe may, or may not, take notice of your post.
I understand this but this was more a query to other users of the software and what they have chosen to do.
iam sorry, but all users of our company have this bluescreen/error too (maybe someone of the adobe employees can answer this).
Our company has the same issue on a Win10 Enterprise and we cannot deactive the guard for security reasons!
There must be a way to start the software without canceling security options (GPO).
One thing to note is that the design of Windows is "AN APP CANNOT CAUSE A BSOD". That is not to say they do not happen. What it means is that there is no kind of fault in an app, not even any deliberate way, that an app can be responsible. The fault must be elsewhere: hardware, system, drivers. Here is an analogy: if something is sold as bulletproof and it fails, you do not look for a fault in the bullet.
In theory, it should not be possible to bring Windows to its knees simply by installing an application, and as you say, that is the design. However, I, like the others here, have experienced this very thing by installing Photoshop Elements. On the one hand, I don't understand why Adobe continues to include a component that has been blocked by MS and which is apparently not required. On the other, why is it even possible that this file could cause Windows to become absolutely unusable? This is a failure on the part of both companies.