Surface Pro 3 Applying edu coupon + 150 tradein coupon

Went to Best Buy store # 495 in Baton Rouge LA to buy the Surface Pro 3. I had both coupons with me. The employee who helped me, Sean said only 1 coupon can be used. When I told him to try the other he manually removed the first one and then applied the other. I asked him to keep the first one and then apply the other, but he refused. He told me I could not double-dip with coupons.
I told him others were able to do it, as I see even on these forums but he kept saying best buy does not allow double-dipping. A word he seemed to enjoy using. He also wrote void on my $150 coupon because he already applied it before we had this discussion. And even though he said he cancelled the transaction, I am afraid I cant use the coupon at another store, since it says the written text void right on the coupon, unless I use a white-out or something.

Hello sailtovictory,
I’m sure you were excited to get your hands on a new Surface Pro 3, especially if you had such nice coupons you could use, so it’s regrettable to hear that our store associates were less than accommodating when it came to your request. The experience you describe is far from ideal, and I truly apologize for any frustration this may have caused.   
While we cannot combine most coupon offers, I’m admittedly unsure if this is the case for your two coupons.  As such, I’d like to review your case to see what options we may have available at this time. I know you mentioned our associate voided your $150.00 coupon as you already applied it; however, was a purchase ultimately made? If so, please send me a private message with your Customer Service Pin (found towards the middle of your receipt). To send me a message, please log into the forum and click on the blue button included in my signature below.
I hope to hear from you soon,
Alex|Social Media Specialist | Best Buy® Corporate
 Private Message

Similar Messages

  • Denied my working tablet for the surface pro 3 $50 GC and 150 coupon

    I looked around the forum and I see people have traded in tablet even though they weren't able to find it on database. I have the azpen android tablet and it works has no scratches or damages. They said because it wasn't in the database they weren't able to do the surface pro 3 trade in promotion for the 50 gc and 150 coupon towards the SP3. I went into two stores and they said the same thing. So what is the deal? The two stores were:
    REGO PARK NY (Store 483)
    8801 Queens Blvd
    Elmhurst, NY 11373
    and 
    GATEWAY BROOKLYN NY (Store 1886)
    369 Gateway Dr
    Brooklyn, NY 11239

    Hello mrso, 
    The Surface Pro 3 trade-in is a spectacular promotion and I'm sure you were looking forward to receiving a $50 Best Buy gift card and $150 coupon towards the new Surface Pro 3!
    As it appears this trade-in promotion has worked like our previous ones, you should be able to trade-in a qualifying tablet even if it isn't in our database via the recycling option we should have available to us. I am terribly sorry if our Rego Park, NY store and Gateway Brooklyn, NY stores were unaware of this ability.
    Our stores should have received communications to provide them with the necessary knowledge to appropriately fulfill this promotion. Please know that I've also reached out to each to ensure they are following the appropriate fulfillment methods for this trade-in, and I would encourage you to return to one of the stores and request assistance with fulfilling this promotion from a manager. 
    Please let me know if you continue to have trouble! 
    Best wishes,
    Tasha|Social Media Specialist | Best Buy® Corporate
     Private Message

  • Tablet not accepted for trade in surface pro 3 150 coupon

    Hi I have a proscan tablet model plt4311. Is it applicable for trade in or not. The store at best buy waterfront Pittsburgh says they cannot accept it. As far as I know the best buy policy says any working tablet will work. Please reply

    Hello Mohitpharma, 
    Thank you for reaching out to us regarding your trade-in! I'm sorry to hear you may have had trouble with trading in a Proscan tablet under our trade-in offer to trade up to the Surface Pro 3. Provided your tablet meets the working qualifications, it should have qualified for this promotion.
    We trust that our stores are kept up-to-date and are knowledgeable in how to process qualifying tablets under such promotions. Sadly, it seems that this promotion ended yesterday, 4/18/15. With that said, as I see you were inquiring about combining three coupons in another post (Movers Coupon, College Student Deals coupon, and the $150 coupon from the Surface Pro 3 trade-in offer), which you will see I've merged with this post. Was this a proactive inquiry, or were you able to successfully trade in your Proscan tablet? 
    Regards, 
    Tasha|Social Media Specialist | Best Buy® Corporate
     Private Message

  • Student discount coupon for Microsoft surface pro 3

    Hi  Its been more than 4 days i have been registered and i have not received coupons on surface pro 3.When i had  chat with best buy rep they said i will get in mail. but none so far. Can i go to local store with my idHelp please Thanks

    Laptop Video Editing PC - http://forums.adobe.com/thread/1369220?tstart=0

  • LR and Surface Pro 3

    Adobe made a big play about how well PS worked on the Surface Pro 3, but I have just got a SP3 and I find that LR (and PS) has serious failings.
    Background: I have a CC subscription for LR and PS, and I have the i7, 8mb, 512gb version of the SP3.
    In particular, in LR (and PS), the stylus right-click options (upper button click, or hold-down) are not recognised. A mouse works, but not the stylus. These options are vital for e.g. points curve editing. I bought the SP3 mainly for photo editing and management while travelling; I'd prefer not to bring a mouse with me.
    Also, in LR the CTRL and SHIFT keys are vital, but on the SP3 you need the physical keyboard to access them properly; the screen keyboard implementation is too clumsy. Perhaps I'm asking for too much here, but I'd hoped for a slicker adaptation to the SP3.
    I am more likely to use LR than PS while travelling, but my question really applies to both.
    Am I missing something? Is better optimisation of LR and PS in the works?

    I do not use lightroom Photoshop runs well on the surface pro 3. You may have a problem with the size of Photoshop's UI. CC 2014 2x UI option works Photoshop UI almost all  Photoshop UI fits one screen withe the 2x UI option enabled.   You would be wise to add a bluetooth mouse. And if you want to use Photoshop im tablet mode without a keyboard look into touchkey. Adobe need to create new touch friendly UI for managing tools use as you uses them.
    For older versions of Photoshop CC and prior you can make a  registry mod and add external Photoshop Manifest to have Widdows scale what Photoshop display. Here is a comparison  of CC 2014 2x UI and Windows scaling. The big difference is Windows scaling also scale the image Photoshop  to a lower resolution while 2x UI does not. Windows scaling presets are 100% 1x,  125% 1.25x, 150%, 1,5x and 200% 2x.

  • Scaling support for surface pro 3

    I'm running the latest version of Windows 8.1 and the latest version of iTunes 12 for Windows. I was hoping with the update, scaling support would be included for high DPI devices like the Surface Pro 3. I was in the Apple store and the retina macbook pros are fine, so they obviously have the technology available to support it. I talked to an employee, and they said wait for iTunes 12 to come out, and it hasn't fixed anything. High DPI displays are still not supported, and I am getting quite angry and impatient. I prefer Windows for my desktop experience, and it seems like Apple is alienating Windows users here. I am going to start looking for alternatives to iTunes in the meantime. Can someone help me out? I know I can disable scaling under properties, but this just makes everything very small, and is very annoying,

    Hello noles200,
    The College Student Deals is an awesome promotion, and its awesomeness is matched by the Surface Pro 3! I apologize if you have been unable to take advantage of this offer due to not receiving any coupon codes to your .edu email address with which you registered.
    It is important to check your Junk/Spam folders in the .edu account you used to register as these emails can occasionally be automatically filtered into that location. Additionally, I would recommend speaking with your school’s IT department in regards to the ability to receive these emails altogether. If you would like to reference the sending email address, it [email protected] Did you receive the verification email after you registered? If not, you may try reregistering on the College Student Deals page on BestBuy.com with your .edu email address.
    For more information on this you may visit our College Student Deals FAQ page here.
    In the event this doesn’t work, please send me a private message with the .edu address you used so I may investigate further. To send me a private message, click on the envelope in the upper right-hand corner while you are logged into the forums.
    Best of luck,
    JD|Social Media Specialist | Best Buy® Corporate
     Private Message

  • Surface Pro 3 Student Discount

    Hello,
    I am interested in purchasing a Surface Pro 3 and receiving the advertised $150 discount.
    I will be attending the University of Nevada, Reno this fall.  Unfortunately they have quit issuing student email addresses (http://www.unr.edu/it/communications/email/new/student-email). Since I do not have an email ending in .EDU, I am unable to receive a discount code via your website.
    Is there a way to prove student status and receive the discount other than an email ending in .EDU?
    Solved!
    Go to Solution.

    Hi JacksonD,
    Not having immediate access to an .EDU e-mail address would certainly make things difficult, but rest assured that I'd be glad to help you out! Please make sure to check your private messages when you can by signing into the forum and then clicking on the letter icon in the upper right-hand corner of the page.
    Best of luck to you this fall!
    Aaron|Social Media Specialist | Best Buy® Corporate
     Private Message

  • 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.

  • 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.

  • PS and LR CC on Surface Pro

    Does anyone have experience running PS (and/or LR) CC on a Surface Pro 3?  Good?  Bad?  Ugly?  Comments or recommendations?

    I do not use lightroom Photoshop runs well on the surface pro 3. You may have a problem with the size of Photoshop's UI. CC 2014 2x UI option works Photoshop UI almost all  Photoshop UI fits one screen withe the 2x UI option enabled.   You would be wise to add a bluetooth mouse. And if you want to use Photoshop im tablet mode without a keyboard look into touchkey. Adobe need to create new touch friendly UI for managing tools use as you uses them.
    For older versions of Photoshop CC and prior you can make a  registry mod and add external Photoshop Manifest to have Widdows scale what Photoshop display. Here is a comparison  of CC 2014 2x UI and Windows scaling. The big difference is Windows scaling also scale the image Photoshop  to a lower resolution while 2x UI does not. Windows scaling presets are 100% 1x,  125% 1.25x, 150%, 1,5x and 200% 2x.

  • 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?

  • Surface Pro 3 is not able to connect to standalone aironet

    Hello,
    we are having issues with several Surface Pro 3 device connecting to a standalone Aironet. Other Device connect to this AP no problem. SP3 connect to other APs (not cisco) no problem. So there seems to be an issue between the two devices. When I look in the logs of the AP I get the following message:
    Jan 15 19:59:52.513: %DOT11-7-AUTH_FAILED: Station 501a.c5e5.aeff Authentication failed
    I tried to run aaa debug but nothing shows up but that message above. We use WPA2 AES/TKIP.
    I proceeded to run debug all on the AP and this is what I got. Keep in mind that we are troubleshooting 501a.c5e5.aeff 
    Jan 15 19:55:19.646: Setting client MAC 501a.c5e5.aeff radio slotunit 0 address 0x7E2CE90
    Jan 15 19:55:19.646:  Adding client 501a.c5e5.aeff client->reap_flags_1 0
    Jan 15 19:55:19.646: Dot11Radio0: Adding client 501a.c5e5.aeff aid 6
    Jan 15 19:55:19.646: dot11_mgmt: drv add resp for client 501a.c5e5.aeff aid 6
    Jan 15 19:55:19.646: dot11_mgmt: dot11_mgmt_sta_ref (ref=2, sta_ptr=0x7530010, mac=501a.c5e5.aeff)
    Jan 15 19:55:19.646: SM: ---Open Authentication 0x7530010: Drv Add Resp (8)
    Jan 15 19:55:19.646: SM:    Drv_Add_InProg (8) --> DONT CHANGE STATE (255)
    Jan 15 19:55:19.646: dot11_mgmt: [168D368F] response from driver for client 501a.c5e5.aeff
    Jan 15 19:55:19.646:  Setting global apsd config before assoc rsp
    Jan 15 19:55:19.646:  dot11_driver_client_apsd_settings Client(501a.c5e5.aeff) not found for APSD settings
    Jan 15 19:55:19.646: about to perform cac before cac resp
    Jan 15 19:55:19.646:  dot11_tsm_delete_ts_not_reassociated:Clean streams not in REASSOC 
    Jan 15 19:55:19.646: dot11_mgmt: [168D36F5] send assoc resp, status[0] to dst=501a.c5e5.aeff, aid[6] on Dot11Radio1
    Jan 15 19:55:19.646: There is nothing to add from qosie_set in ASSOC Rsp
    Jan 15 19:55:19.646: Dot11Radio1: Tx AssocResp client 501a.c5e5.aeff
    Jan 15 19:55:19.646: dot11_aaa_auth_request: Received dot11_aaa_auth_request for client 501a.c5e5.aeff
    Jan 15 19:55:19.646: dot11_aaa_auth_request: SSID: Executive, Mac Address: 501a.c5e5.aeff, auth_algorithm 0, key_mgmt 1027074
    Jan 15 19:55:19.646: AAA/API(00000000): aaa_util_unique_id_alloc(), pc 0x185F920, enter {
    Jan 15 19:55:19.646: AAA/ID(NA): DOT11 allocating
    Jan 15 19:55:19.646: AAA/ID(00000023): Call started 14:55:19 -0500 Jan 15 2015
    Jan 15 19:55:19.646: AAA/DB(00000023): add Intf/7D3D488
    Jan 15 19:55:19.646: AAA/DB(00000023): add DB 7E2910C
    Jan 15 19:55:19.646: AAA/ID(00000023): DOT11 allocated
    Jan 15 19:55:19.646: AAA/API(00000023): } aaa_util_unique_id_alloc()
    Jan 15 19:55:19.646: dot11_mgr_disp_wlccp_update_auth:  unknown auth type 0x1
    Jan 15 19:55:19.646: dot11_aaa_add_dot11_client_entry: AAA Client entry (501a.c5e5.aeff, 4106500) is added to the client list
    Jan 15 19:55:19.646: dot11_aaa_start_auth_sequence: dot11_aaa_start_auth_sequence for client 501a.c5e5.aeff [key_mgmt] = FAC02
    Jan 15 19:55:19.646: dot11_aaa_start_auth_sequence: dot11_aaa_start_auth_sequence for client 501a.c5e5.aeff [key_mgmt] = FAC02
    Jan 15 19:55:19.646: dot11_mgr_sm_start_wpav2_psk: Starting wpav2 4-way handshake for PSK or pmk cache supplicant 501a.c5e5.aeff
    Jan 15 19:55:19.646: dot11_mgr_sm_send_wpav2_ptk_msg1: Starting wpav2 ptk msg 1 to supplicant 501a.c5e5.aeffCould not find station pointer for client 501a.c5e5.aeff. Using vlan number from aaa_client 
    Jan 15 19:55:19.646: dot11_dot1x_send_ssn_eapol_key: wpav2 msg 1 pak_size 121
    Jan 15 19:55:19.646: dot11_dot1x_send_ssn_eapol_key: eapol->length 117
    Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: building PTK msg 1 for 501a.c5e5.aeff
    Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: ptk key len 16
    Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: ptk key data len 22
    Jan 15 19:55:19.646: dot11_dot1x_build_ptk_handshake: wpav2 pmkid[DOT1X]: 0CBC860AAF0DBBA764ED9D51BB113194
    Jan 15 19:55:19.646: dot1x-registry:registry:dot1x_ether_macaddr called
    Jan 15 19:55:19.646: dot11_mgr_disp_client_send_eapol: sending eapol to client 501a.c5e5.aeff on BSSID c025.5ca5.3c40
    Jan 15 19:55:19.646: dot11_mgr_sm_send_wpav2_ptk_msg1: [1] Sent PTK msg 1 to 501a.c5e5.aeff, no timer set
    Jan 15 19:55:19.650: dot11_mgmt: dot11_mgmt_sta_deref (ref=3, sta_ptr=0x7530010, mac=501a.c5e5.aeff)
    Also, on windows end I checked the Event Viewer and I see that SP3 is not getting any response back from the AP. 
    Any help would be greatly appreciated. Thanks.

    I rolled out a batch of these to our wireless network a couple of months back.  A couple of tips:
    - From a wireless perspective these devices are extremely buggy out of the box (I'm not exaggerating).  They basically won't function using the built in wireless with anything other than the most very basic wireless setup of a home router until you apply ALL of the patches and updates for them in Windows Update.  In my case I had to install all the updates via ethernet dongle and/or a Linksys USB Wireless dongle (the drivers were much better for the USB dongle and allowed connectivity to work).  The built in Marvell adaptor looks to be good from a features perspective but poor from a driver perspective.  Once the updates were applied it mostly worked.
    - I experienced a similar problem with FT (Fast Transition) enabled - the SP3 will not connect with FT enabled.  In my view there were two issues - (1) the devices won't even connect if FT is enabled and (2) they don't support the FT feature for seamless roaming.
    I took it up with Microsoft and they acknowledged the problem but wouldn't commit to fixing the buggy behaviour (allowing the connection and ignoring the FT attribute like many older clients do) nor would they commit to when they will support the FT feature (fast roaming).
    These tips might not be the cause of your problem but hopefully they will help you get it up and running.
    Fortunately all of these problems can be fixed with driver updates, so maybe in the future they may end up being pretty good wireless clients afterall :-)

  • 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.

  • 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.

  • MDT 2013 Fails to Format or Partition disk on Surface Pro 3

    I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment.  At first I would get an error that it was unable to format or partition the drive and then after that it
    just reboots after trying for so long.  I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3.  Any help would be great.
    Thanks in advance.
    I am getting the error FAILURE (5210)
    ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

    I think our problem is also hardware failure although without re-imaging a working surface pro 3 I can't be sure.
    I tried what imfusio suggested in this thread.
    https://social.technet.microsoft.com/Forums/en-US/d31384bc-4e96-4a5b-a400-637bd6006d81/failure-5456-unable-to-determine-destination-disk-partition-and-or-drive-surface-pro-3?forum=mdt
    Unfortunately the deployment failed with the same ZTI Error - Unhandled error returned by ZTIDISKPART:
    Object required (424)
    I then rebooted into WinPE and ran diskpart, I could see the two volumes (EFI and OSDisk). I then tried to format the OS disk volume using diskpart. I got a paramater is incorrect error and the disk was no longer visible with a 'list disk' command. So it's
    like the format is putting the disk offline. I'm going to try restore one of these surfaces, apply all firmware updates then re-image. If that doesn't work I'm out of ideas.

Maybe you are looking for

  • Itunes 10.6.0.40 Stops Working

    I have been having trouble accessing ITunes since Thursday March 15th.  I open ITunes and it starts to run Match and download podcasts and usually crashes within a minute.  A couple times I have stopped Match from running and it has not crashed, but

  • IPad 2 light leakage? Does it get worse with time?

    My iPad 2 suffers from the leakage. Question. Will it get worse over time, or WYSIWYG? Regards

  • CS3 not opening on Laptop but will on PC

    I am using a version of CS3 that runs from a USB thumb drive. I have never had problems with PS opening on my desktop PC from this drive. The PC is running Windows 7. So recently I bought a laptop and put Windows 7 on it. For some reason Photoshop wi

  • One CONTROL FILE KO

    Hi all, I read some post from this forum and i found at this : http://forums.oracle.com/forums/login.jspa where user lost all the CONTROL FILE. Instead I have a problem only with one...but I have this error "ORA-00205...." I could start the DB but ca

  • Next Generation?

    Hey Guys, I'm looking into buying a new Mac, and I'm thinking either the 13" Macbook Pro or the Macbook Air. However, I've heard that Apple typically ramps up the hardware of their notebooks around this time of year, so I don't want to jump the gun.