juls

https://www.ghacks.net/2017/01/21/adobe-pushed-insecure-adobe-acrobat-extension-to-chrome-systems/

Had the same problem IE 11 was pretty much unusable. What fixed it for us was making sure "Enable Protected Mode" was not checked. This setting is in Internet Options>Security> Internet & Restricted sites by default for us. We are now applying this via gpo.

All issues I've had so far have been with the built in apps. Booting into audit mode after installation is how I am currently bypassing any updates being applied. As soon as I boot into the computer I run the powershell cmds below to remove all apps first thing. Get-AppxPackage | Remove-AppxPackage Get-AppXProvisionedPackage -online | Remove-AppxProvisionedPackage -online I've also been having trouble reducing the size of the default user profile seeing that mklinks from the appdata no longer work through sysprep.

Yes it is if its included in the default profile.

Windows 10 Edition - Enterprise Windows 10 Build Number - RTM 10240 Default image or customised with apps removed? - Customized all default apps removed - due to sysprep error (will remove all of them anyway) Time taken for a new user to log in, from clicking login button to seeing the desktop - 40 seconds unfrozen, with deep freeze and the computer frozen the time increases to about a minute. Hardware used (if there's a wild difference in results between different kit) - i5, 7200rpm HD, 8gb ram, and the model is a Lenovo m93z. User profile size - Default is 220mb (made a lot of mklinks to transfer adobe data and other various programs out of appdata to another location) Also on our network we are in the process of upgrading our DC's to 2012 r2. The logon speed was timed connected to our 2008 DC's and the w10 computer receiving all policy that a w7 would get. Windows 7 Logon times are about the same with the profile size being around 180mb. We have about 10 GPO's being applied at logon. I've also noticed first logon after deployment takes about 5 minutes or more to logon to local admin. Our group has been contemplating waiting on going to 10 because of various issues we have experienced with sysprep and peripheral compatibility.