Surface Pro 2 using Bitlocker startup PIN

Hi All,
In our enviorment we're using the Microsoft Surface Pro and Microsoft Surface Pro 2 with bitlocker encryption using a startup pin.
The operating system using is Windows 8.1
We're using the folowing GPO settings for Bitlocker encryption:
- Require Additional Authentication at Startup
     - Allow Bitlocker without a comatible TPM > unchecked
     - Configure TPM startup > Allow TPM
     - Configure TPM startup PIN > Allow startup PIN with TPM
     - Configure TPM startup key > Allow startup key with TPM
     - Configure TPM startup key and PIN > Allow startup key and PIN with TPM
- Enable use of BitLocker authentication requiring preboot keyboard input
The Microsoft Surface Pro doesn't have any issues with the startup PIN.
The Microsoft Surface Pro 2 sometimes doesn't respond to the keyboard, there is no difference between a USB keyboard or a Surface Type Cover.
The only difference between the Microsoft Surface Pro and pro 2 is the UEFI bios.
Is there a solution to get bitlocker PIN authentication working on the Surface Pro 2.
The only workaround we've found is hold volume down at startup wich is not a ideal solution to instruct the users.
The oktober firmware upgrade didn't solved this problem.
Laurens van Leeuwen

We have seen the exact same thing as below. For reference, we are re-imaging ours with Windows 8.1 Enterprise Edition.  
In addition to the issues listed below, I can't seem to figure out how to activate the supposed "bios level" on-screen keyboard that was supposed to be added to Surface Pro (v1) in a Firmware flash and should be part of Surface Pro (v2).  Does anyone
have experience with activating that?  I read an article a few months ago that claimed MS had addressed the latter with a flash to Surface 1.  I hope I didn't dream it.  :)
Please address this - I have high level personnel evaluating Surface vs. Dell and this will make a big difference in the final decision! 
<hl>
Bryan E. Johnson
Hi All,
In our enviorment we're using the Microsoft Surface Pro and Microsoft Surface Pro 2 with bitlocker encryption using a startup pin.
The operating system using is Windows 8.1
We're using the folowing GPO settings for Bitlocker encryption:
- Require Additional Authentication at Startup
     - Allow Bitlocker without a comatible TPM > unchecked
     - Configure TPM startup > Allow TPM
     - Configure TPM startup PIN > Allow startup PIN with TPM
     - Configure TPM startup key > Allow startup key with TPM
     - Configure TPM startup key and PIN > Allow startup key and PIN with TPM
- Enable use of BitLocker authentication requiring preboot keyboard input
The Microsoft Surface Pro doesn't have any issues with the startup PIN.
The Microsoft Surface Pro 2 sometimes doesn't respond to the keyboard, there is no difference between a USB keyboard or a Surface Type Cover.
The only difference between the Microsoft Surface Pro and pro 2 is the UEFI bios.
Is there a solution to get bitlocker PIN authentication working on the Surface Pro 2.
The only workaround we've found is hold volume down at startup wich is not a ideal solution to instruct the users.
The oktober firmware upgrade didn't solved this problem.
Laurens van Leeuwen
</hl>
-- From the Dark Recesses of the Decaying Mind of: Bryan E. Johnson

Similar Messages

  • Photoshop CS6 Brush pressure sensitivity not working on the Microsoft Surface Pro.

    I have just purchased a Microsoft Surface Pro in anticipation of running Photoshop on it.  I installed Photoshop and tried to do some sketches.  I created a new file and started sketching.  I Immediately felt like something was wrong.  I checked my brush settings and saw the pressure sensitivity was not available.  Everytine I tried to turn it on it was marked with an exclamation point. 
    Does anybody know if Adobe is supporting the new pressure sensitive pen from microsoft, or if there is some sort of setting that I am missing?  I have tried sketchbook pro 2011, and that works amazingly well with the pen.  I hope someone can help me along here, because if this tablet can truely run photoshop, it would be a Game Changer.

    Just curious.... has any of you tried the shape dynamics in photoshop and turning on pen pressure?
    and in illustrator to modify the size to pressure and variation to maximum? (and of course select that brush preset that you just modified and draw with it using SHIFT+B for blob brush or B for regular brush)
    I am also interested in purchasing a Surface pro so please report if this helps.
    what I recently discovered in other forums is that Sketchbook Pro works flawlessly in desktop mode. Sketchbook Express in the APP mode doesn't support pressure yet.
    there is no official confirmation that the surface pro uses a wacom digitizer, however a few artist friends of mine have gone to the microsoft store... brought their own wacom pens (cintiq 15x pen - older models that works with general tabletpcs) and the pro recognized it. which means that it is a wacom digitizer. it wouldn't make sense if a wacom pen works with a different digitizer board like N-trig.
    also read in another forum about adobe using wintab and windows 8 wintab drivers are not there yet.
    anyway... I'd be glad to know if this works or not
    thanks!

  • Itunes Video Lag on the microsoft surface Pro

    HI,
    I recently purchased a Microsoft surface pro and installed itunes on it to watch all of my store bought series, however i noticed that as soon as i started to watch my purchases the HD content especially would stutter, lag and de sync from the audio playing.
    i was wondering if anyone had similar problems or if anyone knows of a solution
    so far i have tried switching the audio from itunes properties, and it did not work.
    thanks

    Just curious.... has any of you tried the shape dynamics in photoshop and turning on pen pressure?
    and in illustrator to modify the size to pressure and variation to maximum? (and of course select that brush preset that you just modified and draw with it using SHIFT+B for blob brush or B for regular brush)
    I am also interested in purchasing a Surface pro so please report if this helps.
    what I recently discovered in other forums is that Sketchbook Pro works flawlessly in desktop mode. Sketchbook Express in the APP mode doesn't support pressure yet.
    there is no official confirmation that the surface pro uses a wacom digitizer, however a few artist friends of mine have gone to the microsoft store... brought their own wacom pens (cintiq 15x pen - older models that works with general tabletpcs) and the pro recognized it. which means that it is a wacom digitizer. it wouldn't make sense if a wacom pen works with a different digitizer board like N-trig.
    also read in another forum about adobe using wintab and windows 8 wintab drivers are not there yet.
    anyway... I'd be glad to know if this works or not
    thanks!

  • Surface Pro Firmware update

    I would like to update our Surface Pro tablets with the latest firmware update that was released. We use WSUS in our environment and it seems as of now the only way to get this update is through Microsoft Update. Has anyone been able to update their surface
    rt/pro's through WSUS yet? I'm not even sure where these updates would be under.

    For anyone else trying to do this. It is currently not possible to update firmware on the Surface Pro using System Center 2012 Configuration Manager plus Windows Intune. Also, it doesn't appear that there's a way to update firmware using Windows
    Intune standalone either. 
    I learned that you can follow the Surface Pro - Enterprise Deployment Quick Start Guide.pdf that can be found with the Surface Pro driver and firmware pack.
    http://www.microsoft.com/en-us/download/details.aspx?id=38826
    You can also view the procedure in the guide here: http://blogs.technet.com/b/deploymentguys/archive/2013/05/16/deploying-drivers-and-firmware-to-surface-pro.aspx
    Hope this helps somebody as this seems to be a grey area for many of us.
    Dave

  • Bitlocker TPM + PIN on MS Surface Pro 3 using MDT

    We are new to MDT 2012 and are trying to create a task sequence for Surface Pro 3 Tablets. Everything is going OK apart from Bitlocker. We are required to enable TPM + PIN (yes I've read the articles saying PIN isn't necessary on tablets, but security
    have decided they still want it). To get TPM + PIN working there are a couple of GP settings required - enabling TPM + PIN and enabling pre-boot keyboards on slates.
    To apply these settings we would normally have to join the domain and put the tablet in the correct OU for that Policy, which requires a restart. However once Policy is applying the restart now forces the corporate data warning message and so doesn't continue
    with the sequence. the only solution I can see is to insert the registry settings for these policy settings into the Task Sequence and not do the restart until the end of the sequence. However this seems very messy and could potentially cause maintenance issues
    further down the line if anything needs changing.
    Does anyone have any solutions to this?

    What we had to do was create a deployment OU that blocked pretty much all the domain GP.  Then at the end of the TS we would move machine to its proper OU.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Using Bitlocker Data Recovery Agent (DRA) on Surface Pro 3

    We currently have the Data Recovery Agent (DRA) configured in our Bitlocker Policy for our Windows 7 Systems, and it works fine. In situations where the Recovery Key for the computer object was not backed up to AD correctly for whatever reason or the computer
    object was deleted, our HelpDesk can connect the encrypted drive to another system, and then use the certificate for the DRA to unlock the drive.
    I'm wondering if the BitLocker DRA Certificate unlock method will work for Surface Pro 3 devices, in the case that that their computer object and normal BitLocker recovery key is deleted or missing in AD for whatever reason. Seeing as how our helpdesk can't
    easily remove the internal HD from a Surface Pro 3 (I think only MS can do this?), I'm wondering if this BitLocker recovery option is still an option for Surface Pro 3's and if it is not then if there is another recommended option for Surface Pro 3's and/or
    other Windows 8.1 Tablets used in an enterprise environment.

    noctlos wrote:
    Using linux-3.18 and -3.19 kernels, with wayland/weston v. 1.7. In its own tty, i try to run weston, and I get the following stderr:
    Could anyone help me to figure this out? Thanks.
    Seems that the problem lies in libinput. Maybe you can report that upstream. I suggest you recompile libinput with debug info and do not strip the binaries to obtain better backtraces.
    Edit:
    I have also tried running `swc-launch -- velox`, and get the following error:
    Running on /dev/tty2
    velox: error while loading shared libraries: libinput.so.5: cannot open shared object file: No such file or directory
    Server exited with status 127
    Restoring VT to original state
    So, perhaps I am having some libinput trouble. Does this seem correct?
    Well, that's a different problem. libinput has several soname bumps because of API and ABI incompatibility. You have to rebuild swc against the newest libinput. (Although I'm not sure if swc developer updated the code to new API)
    Edit 2:
    Just to tack this on here for `gnome-session --session=gnome-wayland --debug`
    I'm not expert on this, it may be related to libinput problem. If you don't include GDK_BACKEND=wayland environment variable when launching gnome-wayland.
    Last edited by jdbrown (2015-03-01 08:04:39)

  • Surface Pro 3 - MBAM/BitLocker/TPM: "An Error Has Occurred" Issue

    We are trying to implement full disk encryption using MBAM Server/Client and BitLocker. We have been successful on standard Windows 7 Ent and Windows 8.1 Ent laptops and the MBAM Console reports encrypted/compliant.
    The Surface Pro 3 running Windows 8.1 Ent however has been a pain in the you-know-what! It just will not work like our laptops. The Event Viewer error we get is as follows:
    "An error occurred while applying MBAM policies.
    Volume ID:\\?\Volume{dfd94fd0-206c-45d1-a19a-6a39019ada1e}\
    Error code:
    0x80310018
    Details:
    You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption."
    For reference, here is our workflow:
    1. Enable TPM in UEFI.
    2. Install .NET 3.5 since this is apparently a Windows 8.1 requirement for MBAM. Reboot. Install related updates from Microsoft Update. Reboot.
    3. Verify relevant MBAM & BitLocker GPOs are applied by running "gpupdate /force" in an elevated command prompt. Reboot.
    4. Run the following elevated PowerShell commands and then reboot:
    $tpm=get-wmiobject -class Win32_Tpm -namespace root\cimv2\security\microsofttpm
    $tpm.DisableAutoProvisioning()
    $tpm.SetPhysicalPresenceRequest(22)
    5. Install MBAM Client 2.5 and KB2975636 hotfix.
    6. Run MBAMClientUI.exe and set PIN. On our laptops, encryption begins, but on the Surface Pro 3 we get a generic "An error has occurred". Event Viewer shows the above error.
    Can anyone help?? There has got to be others that have used MBAM on the Surface Pro 3.

    More testing today and I *think* I may have found my issue.
    I failed to mention that on step 5 above, I have been rebooting after installing the MBAM Client and hotfix. It appears that this extra reboot breaks the process and does not allow the MBAM Client to initialize the TPM when running MBAMClientUI.exe. If I do
    not reboot, then everything seems to work great.

  • How do I enable BitLocker support (unlock drive) in WinPE 5.0 (on Surface Pro 2)?

    Hi,
    I have a Microsoft Surface Pro 2 and I am running Windows 8.1 Pro Update 1.
    I have been unsuccessful at building an image that provides BitLocker support.  I searched around the internet and found many posts.  Eventually, I ended up trying to build it with the various added packages I noted.  However, in the end,
    none worked and this is the message I am getting after booting into my WinPE environment:
    manage-bde.exe - Application Error
    The instruction at 0xa20afa3b referenced memory at 0x0000013d.
    The memory could not be read.
    Click on OK to terminate the program
    Here are the commands I ended up using to build my WinPE image:
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-FMAPI.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-SecureStartup.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-EnhancedStorage.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-us\WinPE-Scripting_en-us.cab"
    But even with all that included, I still have the same error about the memory.
    Does anyone have a WinPE 5.0 x64 bootable environment working on a TPM-enabled machine?  If so, how did you build your custom WinPE environment?
    Thanks!

    You have to install the MUI files as well... for English:
    dism /image:C:\boot\macrium\mount /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\en-US\WinPE-SecureStartup_en-us.cab"
    This applies to any package that installs executables, it'll have a seperate MUI package that has to be installed or you get a non-sense error about memory that can't be read. Also, MS thanks for the wonderful error message, really went the extra mile to
    throw everyone under the bus.

  • Add a pin to bitlocker startup

    hi all, I updated my T500 to use Bitlocker with the TPM. Now, to further secure it against brute force password attacks, I want to add a PIN to the startup.  I see that gpedit.msc option to Require additional authentication at startup but I am not sure of the sequence of events.
    With bitlocker already protecting my C drive, if I set the option to Require TPM startup pin, where do I set the initial pin? When I look at the C drive options it doesn't show anything other than suspend, or manage. Manage only shows save or print recovery key again.
    So, how do I tell bitlocker and the tpm to use a pin and where do I set that pin? Do I need to decrypt, set the policy, then re-encrypt? I do not want to get locked out with it wanting a pin I have not yet set.
    Any help appreciated - MS online help is not clear at all on how these options should work.
    thanks
    Solved!
    Go to Solution.

    I know this post is kinda old but I just figured out this problem myself so thought I'd share. This is for those of us that turned bitlocker on prior to doing any configurations on the generic Windows 7 install and wish to add PIN functionality on top of the TPM after the fact.
    (1) First go into your Group Policy (run-> gpedit.msc) as an administrator. In the group policy settings, goto
    Local Computer Policy > ..... >Bitlocker Drive Encryption > Operating Systems Drives
    Find 'Require additonal authentication at startup', and set to enable. Then under the title for 'Configure TPM startup pin', set to "Require startup PIN with TPM". Apply/save and exit.
    (2) Now goto your command (CMD) prompt as an administrator. We will now force Bitlocker to use both TPM and PIN. Type in:
    manage-bde -protectors -add c: -TPMAndPIN
    where 'c:' is your drive. If in doubt, look at some examples first by adding the "-?" command at the end, e.g. "manage-bde -protectors -?"
    This will lead to a command line prompt for you to enroll a PIN. This has to be numbers. If you want to use letters, you have to go back to Group Policy (step 1) and do the addional step of enabling Enhanced startup PINS.
    Now after all this is done, if successful, you can see that the options have changed when entering the "Manage bitlocker" GUI under control panels. Furthermore, when you first bootup into windows, you should be prompted for a preboot authentication PIN. Dont forget to backup your recovery keys just in case they prompt you of course.

  • Surface Pro 3 boots to BitLocker Recovery everytime

    No matter what, Surface Pro 3 boots to the BitLocker Recovery screen every time. I've tried to do a clean Windows 8.1 installation and it still goes to the BitLocker Recovery screen.
    If I press Esc, it goes to this screen:
    Any suggestion is much appreciated.

    Hi Charlie,
    Here is a link for reference of getting into the scenarios ,the hyperlink in it may be more comprehensive :
    Issues Resulting in Bitlocker Recovery Mode and Their Resolution
    http://blogs.technet.com/b/askcore/archive/2010/08/04/issues-resulting-in-bitlocker-recovery-mode-and-their-resolution.aspx
     “I've tried to do a clean Windows 8.1 installation and it still goes to the BitLocker Recovery screen.”
    Do you mean the recovery screen will occur even after we have made a clean installation ? How did you made a clean installation ?Have the drive been formatted ?
    Usually the bitlocker is used to protect the data in the drive ,it should be usable after we formatted it by doing a clean installation. After all it is meaningless after we have formatted the drive .According to the link
    Please check your symptom according to the link ,it is recommended to unplug all the external device when you performed a clean installation .
    Best regards

  • Image down to a Surface Pro with Windows 8.1 Enterprise use PXE fails at Driver Pack Install

    I am using SCCM 2012 SP1 running on windows server 2008 R2 deploying to windows Surface Pro, I am deploying Windows 8.1 Enterprise using PXE.
    It gets the pxe response, formats the HD, deploys the image, downloads the driver package, but when it installs the driver package I get a (0xC0000135) error. When it finishes it boots to windows 8.1 but is missing it's drivers. Here is the dism.log
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 Scratch directory set to 'C:\_SMSTaskSequence\PkgMgrTemp\'. - CDISMManager::put_ScratchDir
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2014-06-10 15:49:06, Info                  DISM   PID=160 TID=1704 Successfully loaded the ImageSession at "X:\WINDOWS\Pkgmgr" - CDISMManager::LoadLocalImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE:
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE:
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Executing command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows"
    /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\FolderProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\WimProvider.dll. -
    CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\VHDProvider.dll. -
    CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\ImagingProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Loading Provider from location X:\WINDOWS\Pkgmgr\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Connecting to the provider located at X:\WINDOWS\Pkgmgr\CompatProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2014-06-10 15:49:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    [160] [0x80070002] FIOReadFileIntoBuffer:(1415): The system cannot find the file specified.
    [160] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [160] [0xc142011c] WIMGetMountedImageHandle:(2568)
    2014-06-10 15:49:06, Info                  DISM   DISM WIM Provider: PID=160 TID=1704 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM VHD Provider: PID=160 TID=1704 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider VHDManager - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM VHD Provider: PID=160 TID=1704 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Getting Provider WimManager - CDISMProviderStore::GetProvider
    2014-06-10 15:49:06, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    [160] [0x80070002] FIOReadFileIntoBuffer:(1415): The system cannot find the file specified.
    [160] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
    [160] [0xc142011c] WIMGetMountedImageHandle:(2568)
    2014-06-10 15:49:06, Info                  DISM   DISM WIM Provider: PID=160 TID=1704 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Imaging Provider: PID=160 TID=1704 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 physical location path: C:\ - CDISMManager::CreateImageSession
    2014-06-10 15:49:06, Info                  DISM   DISM Manager: PID=160 TID=1704 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2014-06-10 15:50:07, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
    2014-06-10 15:50:07, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
    2014-06-10 15:50:07, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0xc0000135)
    2014-06-10 15:50:07, Warning               DISM   DISM Manager: PID=160 TID=1704 A problem ocurred loading the image session. Retrying...  - CDISMManager::CreateImageSession(hr:0xc0000135)
    2014-06-10 15:50:07, Info                  DISM   DISM Manager: PID=160 TID=1704 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2014-06-10 15:51:08, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
    2014-06-10 15:51:08, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
    2014-06-10 15:51:08, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0xc0000135)
    2014-06-10 15:51:08, Error                 DISM   DISM Manager: PID=160 TID=1704 Failed to load the image session from the temporary location: C:\_SMSTaskSequence\PkgMgrTemp\82E1FB72-A2BA-4355-B95D-2AC1A905B6D4
    - CDISMManager::CreateImageSession(hr:0xc0000135)
    2014-06-10 15:51:08, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=C0000135
    2014-06-10 15:51:08, Error                 DISM   DISM.EXE: Unable to start the servicing process for the image at 'C:\'. HRESULT=C0000135
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE:
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2014-06-10 15:51:08, Info                  DISM   DISM.EXE:
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2014-06-10 15:51:08, Info                  DISM   DISM Provider Store: PID=160 TID=1704 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    Hi,
    This might cause the newer version .wim cannot be modified by the lower version dism.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Using a Surface Pro 2 to Sign PDF's?

    I'm a Realtor and when I create new documents for a transacton they come from Zip Forms in PDF format.
    I have been trying to figure out a way to be able to sign these PDF's on a tablet. Current in Acrobat reader I can use the pen selection in the options but there is no way to control the "point" of the pen and it essentially looks like a really FAT marker in the signature areas, pretty much unuseable.
    I've tried a Galaxy Note 10.1 2014 Edition, found the same problem.
    If I use Acrobat Pro instead (and thus paying for acrobat then), would that give me the option to do this?
    Or, should I use something like the Surface Pro 2 instead with normal acrobat (shopping for a tablet now anyway)?
    Or would I need BOTH for that to work?
    I figure there has got to be a way to do on screen signatures in Acrobat on PDF's...I cannot possibly be the only person wanting to do this?
    Thanks!

    This forum is actually about the Cloud, not about using individual programs
    Once your program downloads and installs with no errors, you need the program forum
    If you start at the Forums Index http://forums.adobe.com/index.jspa
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll

  • How can I display a slideshow from my Macbook pro on a projector using a nine pin connection?

    I have prepared a slideshow that I would like to show to a group of people using a projector and screen.  I know the projector uses a nine pin connection but I don't have anything like that on my MAC.  Is there a connecting wire that I could purchase that would use the USB port, or any other and then fit the nine pin?
    My Macbook Pro was purchased in the summer of 2012.
    Thank you.

    Dianita,
    Normally you would need a mini dvi to VGA adapter. VGA is 15 pin connection, serial is 9 pin, are you certain about the pin count?
    Check the projector pin count, as this would rather unusual. If you discover that you need a 15 pin, you can use the above mentioned adapter plugged into a standard VGA cable. Available at Apple store, or do a search online.

  • Using a Mac and a Surface Pro with the same catalog?

    I am using CC on my Mac as my primary computer. I'm thinking of getting a Surface Pro to use as a second computer.
    1. Are there any issues with opening and saving a catalog back-and-forth between a Mac and a PC? I'm thinking of doing it via Dropbox.
    2. Has anyone used LR on a Surface Pro? Can everything be done via touch? Does it work well? I'd like to mainly be able to go through all of my photos and tag and rate them on the Surface.
    Thanks.

    Using dropbox seems to be one of the choices people make when working with the same catalog on multiple computers. It reportedly works well as long as you ensure that you allow ample time for synchronization.
    I cannot answer your question about the Surface Pro. You could download the trial version of Lightroom and evaluate for 30 days and then decide for yourself.
    Adobe - Lightroom : For Windows : Adobe Photoshop Lightroom 5.7.1

  • Installed Thunderbird on second machine(Surface Pro 3 128) using exact settings, can send but not recieve

    No error messages, looks as if it is receiving but nothing. Setup exactly like windows 7 machine. Auto settings do and did not work on other machine but the settings my ISP provided do. Have emulated these on the Surface Pro. No recieve

    As per your request
    Application Basics
    Name: Thunderbird
    Version: 31.0
    User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0
    Profile Folder: Show Folder
    (Local drive)
    Application Build ID: 20140717165725
    Enabled Plugins: about:plugins
    Build Configuration: about:buildconfig
    Memory Use: about:memory
    Mail and News Accounts
    account2:
    INCOMING: account2, , (none) Local Folders, plain, passwordCleartext
    account3:
    INCOMING: account3, , (imap) mail.fritzsching.us:143, alwaysSTARTTLS, passwordCleartext
    OUTGOING: mail.fritzsching.us:587, plain, passwordCleartext, true
    Crash Reports
    Extensions
    Important Modified Preferences
    Name: Value
    browser.cache.disk.capacity: 358400
    browser.cache.disk.smart_size.first_run: false
    browser.cache.disk.smart_size.use_old_max: false
    browser.cache.disk.smart_size_cached_value: 358400
    extensions.lastAppVersion: 31.0
    font.name.monospace.el: Consolas
    font.name.monospace.tr: Consolas
    font.name.monospace.x-baltic: Consolas
    font.name.monospace.x-central-euro: Consolas
    font.name.monospace.x-cyrillic: Consolas
    font.name.monospace.x-unicode: Consolas
    font.name.monospace.x-western: Consolas
    font.name.sans-serif.el: Calibri
    font.name.sans-serif.tr: Calibri
    font.name.sans-serif.x-baltic: Calibri
    font.name.sans-serif.x-central-euro: Calibri
    font.name.sans-serif.x-cyrillic: Calibri
    font.name.sans-serif.x-unicode: Calibri
    font.name.sans-serif.x-western: Calibri
    font.name.serif.el: Cambria
    font.name.serif.tr: Cambria
    font.name.serif.x-baltic: Cambria
    font.name.serif.x-central-euro: Cambria
    font.name.serif.x-cyrillic: Cambria
    font.name.serif.x-unicode: Cambria
    font.name.serif.x-western: Cambria
    font.size.fixed.el: 14
    font.size.fixed.tr: 14
    font.size.fixed.x-baltic: 14
    font.size.fixed.x-central-euro: 14
    font.size.fixed.x-cyrillic: 14
    font.size.fixed.x-unicode: 14
    font.size.fixed.x-western: 14
    font.size.variable.el: 17
    font.size.variable.tr: 17
    font.size.variable.x-baltic: 17
    font.size.variable.x-central-euro: 17
    font.size.variable.x-cyrillic: 17
    font.size.variable.x-unicode: 17
    font.size.variable.x-western: 17
    gfx.direct3d.last_used_feature_level_idx: 0
    mail.openMessageBehavior.version: 1
    mail.winsearch.firstRunDone: true
    mailnews.database.global.datastore.id: d9fd22c3-e9b1-446e-8184-ee4c6031bbb
    network.cookie.prefsMigrated: true
    places.database.lastMaintenance: 1406957724
    places.history.expiration.transient_current_max_pages: 104858
    Graphics
    Adapter Description: Intel(R) HD Graphics Family
    Vendor ID: 0x8086
    Device ID: 0x0a16
    Adapter RAM: Unknown
    Adapter Drivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
    Driver Version: 10.18.10.3496
    Driver Date: 3-7-2014
    Direct2D Enabled: true
    DirectWrite Enabled: true (6.3.9600.16384)
    ClearType Parameters: ClearType parameters not found
    WebGL Renderer: false
    GPU Accelerated Windows: 2/2 Direct3D 10
    AzureCanvasBackend: direct2d
    AzureSkiaAccelerated: 0
    AzureFallbackCanvasBackend: cairo
    AzureContentBackend: direct2d
    JavaScript
    Incremental GC: 1
    Accessibility
    Activated: 1
    Prevent Accessibility: 0
    Library Versions
    Expected minimum version
    Version in use
    NSPR
    4.10.6
    4.10.6
    NSS
    3.16.2 Basic ECC
    3.16.2 Basic ECC
    NSS Util
    3.16.2
    3.16.2
    NSS SSL
    3.16.2 Basic ECC
    3.16.2 Basic ECC
    NSS S/MIME
    3.16.2 Basic ECC
    3.16.2 Basic ECC

Maybe you are looking for

  • Unable to open Captivate v5.5 with Windows 7

    A colleagure created a project using Captivate v5.5 / Win XP. Now she is trying to open it with Captivate v5.5 but with newly installed Win 7. After clicking on the file to open it, the progress bar stops at 30% and nothing else happens. The project

  • Solman Document Access thro portal

    hi I wanted to know if we store the documents on SOLMAN, can they be accessed using portal. if yes may i know how

  • PDF File opening error

    Hi, I have an BSP application in which I am fetching the pdf file data from an oracle table to a variable of data type xstring. Now I have to display this xstring again in pdf format in this BSP. The pdf file is generated but while opening it is givi

  • Migrate podcast settings to a new computer

    I'm bringing up a new computer and am looking for a way to export my podcast settings from my old computer and import it into my new computer. Does anyone know how to do this? Thanks

  • Howto resolve the path to the class file

    hi @ all, i'm currently developing a package for ldap operations. now i want to write down all the real basic configuration for that package into a xml file which i want to save in the folder where the compiled class files are stored. my problem is t