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

Similar Messages

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

TS Failing only on one Surface Pro booting to USB - 0x80004005

This is only happening with one of many Surface Pro's
I am unsure what would cause this, booting from USB in a hub with USB Network Adapter.
<![LOG[LOGGING: Finalize process ID set to 812]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="tslogging.cpp:1495">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816"
file="bootshell.cpp:1052">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="util.cpp:963">
<![LOG[Debug shell is enabled]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:1063">
<![LOG[Waiting for PNP initialization...]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:60">
<![LOG[RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.874+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="configpath.cpp:186">
<![LOG[WinPE boot path: D:\SOURCES\BOOT.WIM]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:211">
<![LOG[Booted from removable device]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="configpath.cpp:241">
<![LOG[Found config path D:\]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:545">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:579">
<![LOG[D:\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:596">
<![LOG[D:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:610">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="19:45:17.890+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[Starting DNS client service.]LOG]!><time="19:45:23.907+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:663">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820"
file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:45:24.414+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="820" file="bootshell.cpp:939">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604"
file="tsmbootstrap.cpp:1129">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:1130">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="util.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="resourceutils.cpp:169">
<![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604"
file="tsmbootstrap.cpp:963">
<![LOG[Failed to open PXE registry key. Not a PXE boot.]LOG]!><time="19:45:24.492+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:844">
<![LOG[Media Root = D:\]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1000">
<![LOG[WinPE boot type: 'Ramdisk:SourceIdentified']LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmbootstrap.cpp:779">
<![LOG[Failed to find the source drive where WinPE was booted from]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="2" thread="604" file="tsmbootstrap.cpp:1036">
<![LOG[Executing from Media in WinPE]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1041">
<![LOG[Verifying Media Layout.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:1581">
<![LOG[MediaType = BootMedia]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2565">
<![LOG[PasswordRequired = false]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2591">
<![LOG[Found network adapter "ASIX AX88772 USB2.0 to Fast Ethernet Adapter" with IP Address 10.0.192.203.]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="604" file="tsmbootstraputil.cpp:474">
<![LOG[Running Wizard in Interactive mode]LOG]!><time="19:45:24.508+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawizardcontrol.cpp:2766">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:45:24.524+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Activating Welcome Page.]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:131">
<![LOG[Loading bitmap]LOG]!><time="19:45:24.542+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsremovablemedia.cpp:322">
<![LOG[no password for vars file]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:247">
<![LOG[Spawned thread 1020 to download policy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmediawelcomepage.cpp:405">
<![LOG[Entering TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:527">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00']LOG]!><time="19:47:18.401+480"
date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="environmentscope.cpp:284">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="environmentscope.cpp:659">
<![LOG[Setting LogMaxSize to 1000000]LOG]!><time="19:47:18.401+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:555">
<![LOG[Setting LogMaxHistory to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:556">
<![LOG[Setting LogLevel to 0]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:557">
<![LOG[Setting LogEnabled to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:558">
<![LOG[Setting LogDebug to 1]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:559">
<![LOG[UEFI: true]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:569">
<![LOG[Loading variables from the Task Sequencing Removable Media.]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:584">
<![LOG[Loading Media Variables from "D:\sms\data\variables.dat"]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsremovablemedia.cpp:322">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="util.cpp:963">
<![LOG[Setting SMSTSLocationMPs TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSMediaGuid TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaPackageID TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBootMediaSourceVersion TS environment variable]LOG]!><time="19:47:18.417+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSBrandingTitle TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertSelection TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSCertStoreName TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSDiskLabel1 TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSHTTPSPort TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSIISSSLState TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaPFX TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaSetID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSMediaType TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSPublicRootKey TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSRootCACerts TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteCode TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSiteSigningCertificate TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSSupportUnknownMachines TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSTimezone TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSUseFirstCert TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:604">
<![LOG[Root CA Public Certs=]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:615">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:621">
<![LOG[Support Unknown Machines: 1]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:632">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:675">
<![LOG[No hook is found to be executed before downloading policy]LOG]!><time="19:47:18.432+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:699">
<![LOG[Authenticator from the environment is empty.]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:838">
<![LOG[Need to create Authenticator Info using PFX]LOG]!><time="19:47:18.448+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:850">
<![LOG[Initialized CStringStream object with string: 1A069864-04BE-4B67-B83D-10B87060836D;2014-01-18T03:47:18Z.]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="stringstream.cpp:101">
<![LOG[Using user-defined MP locations: http://CA1AP03P.cameco.com]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:911">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:18.526+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Set media certificates in transport]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9558">
<![LOG[IP: 10.0.192.203 10.0.192.0]LOG]!><time="19:47:18.557+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:9579">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 GET /SMS_MP/.sms_aut?MPLOCATION&ir=10.0.192.203&ip=10.0.192.0]LOG]!><time="19:47:18.573+480" date="01-17-2014" component="TSMBootstrap"
context="" type="1" thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="libcrypt.cpp:1914">
<![LOG[Default CSP Type is 24]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libcrypt.cpp:1915">
<![LOG[New settings:]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:925">
<![LOG[    site=CA1,CA1, MP=http://CA1AP03P.cameco.com, ports: http=80,https=443]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020"
file="tsmediawizardcontrol.cpp:927">
<![LOG[    certificates are received from MP.]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="tsmediawizardcontrol.cpp:931">
<![LOG[Set authenticator in transport]LOG]!><time="19:47:19.715+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:7751">
<![LOG[Preparing Client Identity Request.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:583">
<![LOG[    Setting transport.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:586">
<![LOG[    Setting SourceID = 1A069864-04BE-4B67-B83D-10B87060836D.]LOG]!><time="19:47:19.747+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:590">
<![LOG[    Setting site code = CA1.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:595">
<![LOG[Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.]LOG]!><time="19:47:19.762+480" date="01-17-2014" component="TSMBootstrap" context=""
type="1" thread="1020" file="utils.cpp:1314">
<![LOG[    Setting SMBIOS GUID = 3F9CD3F3-201B-D0BE-FB7A-B6EE09756535.]LOG]!><time="19:47:20.419+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020"
file="tspolicy.cpp:623">
<![LOG[    Adding MAC Address 00:50:B6:4D:18:2D.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:642">
<![LOG[Executing Client Identity Request.]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tspolicy.cpp:666">
<![LOG[Requesting client identity]LOG]!><time="19:47:20.450+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="1020" file="libsmsmessaging.cpp:5760">
<![LOG[Setting message signatures.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1297">
<![LOG[Setting the authenticator.]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:1327">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: CA1AP03P.cameco.com:80 CCM_POST /ccm_system/request]LOG]!><time="19:47:20.465+480" date="01-17-2014" component="TSMBootstrap" context="" type="1"
thread="1020" file="libsmsmessaging.cpp:8621">
<![LOG[Request was succesful.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="libsmsmessaging.cpp:8956">
<![LOG[pNext != NULL, HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,1972)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[reply has no message header marker]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:1972">
<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="libsmsmessaging.cpp:5868">
<![LOG[Failed to get client identity (80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="libsmsmessaging.cpp:6163">
<![LOG[oClientIdentity.RequestClientIdentity(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\tspolicy.cpp,668)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0"
thread="1020" file="tspolicy.cpp:668">
<![LOG[Failed to read client identity (Code 0x80004005)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="3" thread="1020" file="tspolicy.cpp:668">
<![LOG[TS::Policy::GetClientIdentity (&httpTransport, sSiteCode.c_str(), sMediaGuid.c_str(), sClientGUID, sNetbiosName, bUnknown, sServerName, sServerRemoteName, sImportedClientIdentity), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,965)]LOG]!><time="19:47:20.512+480"
date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:965">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="1020" file="tsmediawizardcontrol.cpp:1378">
<![LOG[pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303)]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap"
context="" type="0" thread="1020" file="tsmediawelcomepage.cpp:303">
<![LOG[Setting wizard error: An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time="19:47:20.512+480" date="01-17-2014"
component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawizardcontrol.cpp:1547">
<![LOG[WelcomePage::OnWizardNext()]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediawelcomepage.cpp:340">
<![LOG[Skipping Confirmation Page.]LOG]!><time="19:47:20.512+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaconfirmationpage.cpp:170">
<![LOG[Skipping Task Sequence Selection Page.]LOG]!><time="19:47:20.528+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediataskselectionpage.cpp:118">
<![LOG[Skipping Variables Selection Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediavariablesselectionpage.cpp:155">
<![LOG[Skipping Resolve Progress Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediaresolveprogresspage.cpp:96">
<![LOG[Activating Finish Page.]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="0" thread="604" file="tsmediafinishpage.cpp:107">
<![LOG[Loading bitmap]LOG]!><time="19:47:20.544+480" date="01-17-2014" component="TSMBootstrap" context="" type="1" thread="604" file="tsmbootstrap.cpp:1228">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:857">
<![LOG[The command completed successfully.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:939">
<![LOG[Successfully launched command shell.]LOG]!><time="19:47:52.061+480" date="01-17-2014" component="TSBootShell" context="" type="1" thread="816" file="bootshell.cpp:430">

Duplicate：
http://social.technet.microsoft.com/Forums/en-US/d51d50d5-741a-48a4-832a-bdeec58770cd/one-surface-pro-giving-0x8004005-error-when-looking-for-task-sequence?forum=configmanagerosd
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.

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.

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 boot failure loop

We have a Surface Pro 3 tablet deployed on our network in the office. Since yesterday, when it boots up, we see "Preparing bitlocker recovery" and then a blue screen comes up saying
"There was a problem
Restart your PC to try again
It looks like something didnt load correctly. Restarting might fix the problem. If this happens more than once, you might also be able to find help by searching online for the specific error code
Error code: 8007139f"
I have tried holding the volume down button and pressing the power button to get to BIOS in order to boot from the network and reimage it, no luck. I have tried booting up on a USB drive no luck, blue screen keeps coming.
Please note, our GPO as of right now, disable all bitlocker policies. I am not sure how to pass this.
Thanks,

This forum is for POSReady 7. the Surface forum can be found here:
http://www.surfaceforums.net/forums/microsoft-surface-pro-3.49/
www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Arch doesn't boot up after Windows Update on Surface Pro 3

Hi all,
I am using a Microsoft Surface Pro 3. I have a persistent installation of Arch on a USB drive. It works very well on the Surface. The only problem I am facing is, whenever I run Windows Update, I am not able to boot from the USB Arch installation after that. It just guides me to the BitLocker recovery page. The only way to boot from the USB drive is to install GRUB on the EFI partition again. It'll work until the next Windows Update, but then again the same thing repeats itself. I am stumped as to how to resolve this.
Disabling BitLocker doesn't work too, as the system then boots straight into Windows instead of going to the BitLocker recovery page.

parag14 wrote:Would efibootmgr help in any way?
You can check the boot order by using:
efibootmgr
You can set the boot order using:
# efibootmgr -o xxxx,yyyy,zzzz
Replace the letters with the bootnumbers given by the first command.
You can probably use this method to reset Arch at the top of the list rather than re-installing GRUB.

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.

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.

Surface Pro 3 PXE Boot Error

Hi there,
I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
Wizard Error:
A connection to the deployment (my deployment share) could not be made.
The following network device did not have a driver installed.
PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
PLEASE HELP!

I bought a Belkin USB2.0 adapter and connected to my Pro 3 while the Pro 3 ethernet adapter is connected as well. So 2 network cables are needed. I pxed boot using the Pro 3 ethernet adapter and deploy the image using the Belkin2.0 adapter. Error didnt
come back and deployment was successful. I mean this is a workaround but it works in my environment. The Belkin2.0 drivers are in WinPE and MDT.

Can't PXE boot a Surface Pro 3 after already successfully imaging it

hey guys. To try to eliminate a lot of the initial question that come up with this issue, I figure I will start with established info. Our SCCM environment is healthy, and all images, drivers and apps are distributed to all of our DP's. We can image
PC's and laptops with no issue at all. We use network PXE booting. Using a 64 bit boot image. Needed drivers are injected into the boot image. Firmware on the Surface was updated. Using the Surface NIC dongle. THis dongle was only used to image
this Surface Pro 3 tablet one time. There is no record of the MAC of the dongle in SCCM since I deleted the Surface out, to make it an unknown again.
So, with a lot of trial and error, I was finally able to get this tab to PXE boot, and then successfully image. Was testing out the new windows 8.1 image I had built.
Since it ewas successful I wanted to add all of our apps to the TS and test them out in imaging. Well, I can no longer get this thing to PXE boot. It shows trying to Start PXE over IPv4, then just skips to IPv6, then boots up into windows.
I have delted the secure keys form ther BIOS, then reloaded them. I have tried hte full shut down method (Holding Volume Up and Power for 15 seconds, then waiting for 10 seconds or longer, then trying to PXE boot. I am getting a valid connection fro
mthe dongle.
Nothinhg I try works. Its tries to PXE boot over IPv4, but never gets there. But I can PXE boot any of our PC's or Laptops,m so its just an issue with this damn Surface Pro 3.
ANy advice?

So I finally got our server guy to enable the logging and get that smspxe.log file to be accessible. So here is the info from the log, when I attempt to PXE boot the Surface. I see the last 2 lines where it ignores the request, I just don't know why its
ignoring it.
PXE::CNotifyTimer::TimerSignalFunc SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::ProcessTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Potentially missed device 50:1A:C5:FE:D6:E9 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Cleared Old Devices: 1 / 1 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PurgeOldImages SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Purging old images: 0 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::Init SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::CancelTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::RegisterTimeout SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:347 1ad0230 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 57 Max DHCP Message Size: 05b8
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DF40 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:347 159d1f0 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 57 Max DHCP Message Size: 05b8
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DE50 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 172.028.000.223
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
<============ SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath="xx
BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 172.028.000.223
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
<============ SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:359 1acbeb0 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:359 15a41f0 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 54 Server idenitifier: 172.028.000.015
    Type = 50 Requested IP: 172.028.011.052
    Type = 57 Max DHCP Message Size: ff00
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 54 Server idenitifier: 172.028.000.015
    Type = 50 Requested IP: 172.028.011.052
    Type = 57 Max DHCP Message Size: ff00
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
<============ SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
Ignoring req from [172.028.011.003:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
Ignoring req from [172.028.011.002:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?

Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
Quit and you should be able to install OS X now with your Apple ID and password.
see
http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/

First generation Mac pro booted into utilities and HD recovery, any idea why?

Hi,
My first generation Mac pro booted into utilities and HD recovery when I restared after installing Autodesk sketchbook pro. This isnt the first time this has happened but last time I was not trying to install any software. Fortunatly, I have time machine backups and therefore have managed to recover the HD to a recent date and I intend to do a complete system check when it has finished. The first time this happened I didnt think much of it but now it has happened a second time i'm becoming a little concerned, any idea why this has happened?

I did this the first time it happened so I know that its not that i have the wrong startup disk selected. However, after the recovery had completed I tried the installation again and this time everything went smootly. so as of right now I dont have a problem. Thank you very much for your time and help.

Surface Pro 3 unable to run preview

I tried twice to install Windows 10 9926 on my Surface Pro 3. First, I did an upgrade of my working Windows 8.1. This seemed to work until it got to the desktop, at which point it started cycling something which made it impossible to type and caused a reboot
cycle. I assume a system failure.
After failing to find a way to fix this I ended up cleaning out the entire hard drive and doing a clean Win 10 install. This had the exact same symptom.
So, I finally gave up and went back to Windows 8.1 but wow was this painful. I must have entered my Bitlocker password (all many characters) at least 8 times manually. Then, I had to disable bitlocker (with no indication of how) and then reinstall and then
reenable bitlocker (again with no instructions).
The entire process was about a 2 on a 1...10 rating. At least I now have a working tablet again (but no applications and no data). The 'new' recovery process really needs some user-friendly work. At least one easy way to get into safe mode - please
bring back F8.

Hi there,
I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
Wizard Error:
A connection to the deployment (my deployment share) could not be made.
The following network device did not have a driver installed.
PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
PLEASE HELP!
YOu most likely need to add the microsoft networking adapter to the MDT console, and explicitly add it to the WinPE group. Don't forget to rebuild the deployment share so it regenerates the WinPE iamge.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Surface Pro 3 boots to BitLocker Recovery everytime

Similar Messages

Maybe you are looking for