Surface Pro 3: unable to reimage with MDT 2013

MDT 2013, Windows 8.1 with all udpates in wim file.
Download all drivers and firmware
http://www.microsoft.com/en-us/download/details.aspx?id=38826 to out of box. Update the Surface Ethernet Adapter in winpe. when i am booting i am getting following error, seems like its looking for "VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00"
i search for hwdid, but didn't find anythings. Any help?
orion

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

Similar Messages

  • 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

  • HP Officejet Pro 8100 unable to communicate with printer, but still prints

    Hello,
    I have an Officejet Pro 8100 connected to a Windows XP SP3 computer via USB.  
    When installing  I downloaded the latest drivers off the HP webiste and followed the instructions for installing the printer and connecting via USB.  While installing I only installed the basic print driver.
    The printer appeared to install correctly.
    When printing (test page, or from other programs such as Word or Excell), the printer will actually print the requested document, however, an error box will pop up saying "Unable to communicate with printer".  The only option on the error box is the cancel the current print job.
    Before cancelling the print job, even though the printer actually printed the document, I can still see the document in the print queue until I click the "Cancel" button on the error box.
    I have deleted the printer, uninstalled and reinstalled twice, but the issue persists.
    Any ideas?

    Hi aconway,
    I hate to hear you are having issues.  This could be caused by a port issue, bad USB cable/hub/switch connection, or possibly a spooler or driver issue.  Click Here to run the print and scan doctor (select OS, then click the + sign beside utility diagnostic tools, click the download button next to print and scan doctor). If you would like to learn more about your product, Click Here. 
    Suggestions:
    1. Run the print and scan doctor to identify any port issues
    2. Connect unit directly to PC with new USB cable that meets specifications(no longer than 4-6ft). 
    3. Remove any hubs or switches if being used.  
    Hope this helps!
    Also, remember a click on the Kudos star to the left is a quick "Thanks" for a helpful post.
    Please select the "Accept as Solution" button on the post that best answers your question.
    I appreciate your input !
    Thank You,
    I work for HP.

  • HP Officejet Pro 8600: "Unable to Communicate with Printer" error message

    I receive the error message "Unable to Communicate with Printer" regularly when I print. Sometimes it will print 3 or 4 times just fine before I get this message. Sometimes it happens my first try at printing. I then have to reboot my computer to get it to work again. My OS is Windows 7 and my printer is an HP Officejet Pro 8600. My printer is wired to my computer. I have tried re-installing the printer software but this did not help. I've had this printer for only four months. Started happening after the second month. Any suggestions? 

    I finally solved it.  Reflecting back on previous message boards I decided to try one last time.  Some posters have found the problem in the Antivirus, Firewall protections.  (By the way, I had even upgraded my router with no luck).I have Norton AntiVirus provided by the cable company.1. I turned off everything in the firewall.  Although this left me vulnerable for a few mintues, I needed a fast test.2. It worked!  I was able to print something immediately.3. I went back into the firewall, turned everything back on but turned off an individual switch within the firewall that said to "share the printer. "4. After turning it off, I was able to print and still have the most important parts of the firewall.This ultimately met my needs.Perhaps HP could:1. Do a better job at beta testing prior to release, including various brands of firewalls.  Is there even a beta test process?2. Provide a better description of the error since all indicators within the drivers say the printer is connected.  There should be a message indicating that it's connected but unable to print due to firewall protections.  

  • Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

    I am having an issue with creating a master image with Windows 8.1 and MDT 2013.  
    I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
    except for one issue I have run into, which is successfully capturing this image as a .WIM.
    I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
    to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
    the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE 
    I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
    Any help would be greatly appreciated.

    I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
    test results.
    IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Applying GPO Packs on Server 2012 R2 with MDT 2013

    Hi All,
    I'm having a problem applying a GPO Pack to Server 2012 R2 via MDT 2013 LTI offline media.
    I'm using a standard server task sequence. I've copied my GPO Pack files (created with local GPO export) to the following directory:
    DeploymentShare\Templates\GPOPacks\WS2012R2-MDTGPOPack
    GPOPack.wsf has been modified with the following
    If(Left(strOpVer,3) = "6.3") and (strProductType <> "1") then
             strOS = "WS12R2"
            ElseIf(Left(strOpVer,3) = "6.3") and (strProductType = "1") then
             strOS = "Win81"
            ElseIf(Left(strOpVer,3) = "6.2") and (strProductType <> "1") then
           strOS = "WS12"
    ZTIApplyGPOPack.wsf has been modified with the following:
    If (Left(sOSVersion,3) = "6.3") and oEnvironment.Item("IsServerOS") then
                        sOS = "WS2012R2"
                     oLogging.CreateEntry "Using Windows Server 2012 R2 GPO Pack", LogTypeInfo
                ElseIf (Left(sOSVersion,3) = "6.3") and Not(oEnvironment.Item("IsServerOS")) then
                        sOS = "Win81"
                        oLogging.CreateEntry "Using Windows 8.1 GPO Pack", LogTypeInfo
                ElseIf (Left(sOSVersion,3) = "6.2") and oEnvironment.Item("IsServerOS") then
                    sOS = "WS2012RTM"
    After creating new media I've copied my GPO Pack to the media directory:
    MDTMedia\Content\Deploy\Templates\GPOPacks\WS2012R2-MDTGPOPack
    After I create the ISO and mount in a VM the LTI works fine and I can see in temp\ZTIApplyGPOPack logs that the GPO pack is copied to C:\minint and executed but none of my GP settings are applied.
    Any ideas?
    Thanks in advance

    if you are using offline media (and not over the network deployment) maybe you are having this problem: 
    http://social.technet.microsoft.com/Forums/en-US/be2c05a0-620c-4b64-a82f-18ccc9f6cec5/apply-gpo-pack-offline-media-does-not-apply?forum=mdt

  • Keep extra partition on deployment with MDT 2013

    hello all,
    I am using MDT 2013 to make the
    deployment of some workstations in the company,
    however they all have an extra
    partition (D: \),
    doing some testing I noticed that the
    MDT does clean the entire
    disk, not just on the C:\ drive.
    Is it possible to get the MDT format
    just drive the system keeping
    the extra drive (D:\)?
    Thank you.
    Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

    if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • WINPE User & Keyboard Locale with MDT 2013 & Windows 8.1

    Hi
    I'm using MDT 2013 to deploy win8.1 (ADK 8.1 installed and so on) but I'm having trouble to set the keyboard layout when the Wizard (hta) is loaded.
    We are serving multiple countries so different keyboard settings need to be pushed for our operators when they go through the Wizard in boot.wim/PE phase.
    I opened up the boot.wim file that is generated when you update the deloyment share and generate the litetouch boot iso.
    In there I see that a basic unnattend.xml is being used which specifies the 0409:0000409 (en-US) locale.
    I was under the impression that if we made different Task sequences with their own unnattend.xml we could set the WINPE locale in the WINPE phase via the amd64_xxxx_WINPE_Neutral_xxxx component but it doesn't seem to work that way.
    I know you can provide  a locale in bootstrap.ini but that's a general setting for
    all deployments ...
    Anyone any ideas?
    My next step would be to add skipbdewelcome screen in bootstrap.ini and then have some sections in the customsettings.ini (bound to gateway or site or whatever) to set LOCALEs  in there ....
    jgs

    Hi,
    Sorry for my dilatory reply. According to your description, I doubt whether your Unattened.xml file was set correctly.
    To set default InputLocale during deployment, the correct format should like this:
    <InputLocale>0409:00010409</InputLocale>
    <SystemLocale>en-us</SystemLocale>
    <UILanguage>en-us</UILanguage>
    <UserLocale>en-us</UserLocale>
    From:
    http://technet.microsoft.com/en-us/library/cc749191(v=ws.10).aspx
    In addition, here is another thread which is similar with your problem, may be helpful with your question:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/9af61b5c-6407-44b9-87c4-a4044a94729c/change-regional-settings-keyboard-layout-and-locale-in-task-sequence?forum=configmgrosd
    Roger Lu
    TechNet Community Support

  • My MacBook Pro 2010 unable to link with SSD at SATA 2, 3 Gb speed

    I have a MacBook Pro 13-inch Mid-2010 that I used with the standard 5400 RPM HDD for about a year. Last week I decided to replace it with an SSD, the Corsair Force GT 120 GB to be more precise. I knew that my MacBook Pro model only supports SATA I & SATA II & that the SSD is backwards compatible. I expected (and still expect) the SSD to link up at SATA II 3 Gb speed.
    However, System Profiler gives the following information:
    NVidia MCP89 AHCI:
      Vendor:          NVidia
      Product:          MCP89 AHCI
      Link Speed:          3 Gigabit
      Negotiated Link Speed:          1.5 Gigabit
      Description:          AHCI Version 1.30 Supported
    Corsair Force GT:
      Capacity:          120,03 GB (120.034.123.776 bytes)
      Model:          Corsair Force GT                       
      Revision:          1.3.3
    Benchmark tests show my write & read speeds are at about 100 & 110-130 MB/s. I have searched for a while on this and other forums and not been able to find a way to get negotiated link speed at 3 Gb and then to check whether this solves the rather sluggish performance.
    Some extra info that might be useful:
    -The 1.3.3 firmware of the SSD is the latest available. There are also no updates available via Apple Software Update.
    -The SSD is the only drive in my system. After booting to the Mac OS X Lion DVD I had created, I used the disk tool to partition the new drive with the settings at GUID partition table & HFS+ Journaled. I haven't experienced any other problems.
    -I have reset the SMC, PRAM & NVRAM. This didn't change anything.
    -I haven't installed any Windows version using Boot Camp (yet).
    -System has Boot ROM Version:          MBP71.0039.B0B and SMC Version (system):          1.62f6
    Thank you in advance.

    Guys, have any of you tried these:
    http://support.apple.com/downloads/MacBook_Pro_EFI_Firmware_Update_1_7_
    http://www.engadget.com/2009/06/22/macbook-pro-update-rights-the-wrong-enables-3 gbps-sata-transfer/
    Or solved the problem any other way? I'm thinking on buying a SSD.
    Thanks, and cheers

  • What To Expect With MDT 2013 Multicast from WDS 2008 R2?

    I am having a hard time finding out what to expect when setting this up.  I don't think anyone has posted a demo video showing it in action or even a detailed blog with screenshots.  The only multicast videos I have seen were old ones of WDS multicasting
    that had no reference to MDT.
    What I understand is, once I have working WDS integration with PXE boot, all I need to do is go into properties of the deployment share then select the option to enable multicast support and then update the deployment share.  After that everything is
    supposed to work as long as the network supports multicasting.
    So, how does it work from there?  How do you take advantage of it?
    When I boot up a workstation to deploy to, where do I configure the specific deployment task to use multicasting (or not if I am just imaging a single system)?  When I boot the second and third machine to image, what are the steps to join the ongoing
    multicast? Do you pick the deployment task from the wizard again or does any machine booted to MDT join any in-progress multicast automatically?
    Can you use the wizard to select different optional installed applications for different machines when using a multicast?
    If you are imaging 30 workstations, can you configure it start the multicast when the 30th connection is made or does it start as soon as the first one joins?

    Once multicasting is set in the deployment share it will become the default method of deploying an image for clients connecteing to that deployment point. As far as I'm aware the boot disk does not need to be updated for this to take affect.
    Multicasting in WDS is a rolling session.. It will start as soon as the first client connects and will end when the last machine finishes.  Machines can come and go throughout the session.
    There are more options that can be applied (such as number of machines to wait for) but you need to change registry settings to do this.
    I did have a GUI for this on my to do list.. but never got around to it.  Maybe it's worth another look.

  • Deployed a new computer with MDT 2013, but Windows licensing did not give me an initial grace period

    Hi all,
    Strange issue. I have created a Windows 7 x64 gold image to be deployed. When creating the image, I allowed Sysprep to rearm Windows. I've deployed about 10 computers in the past week and everything has worked fine.
    Yesterday, I deployed another two computers. One works fine, but when I logged into the second one, I was greeted with the you need to activate Windows now screen. I was confused so I ran slmgr /dlv and sure enough my license status was not "Initial
    Grace Period" but instead "Notification." (by the way, it did show remaining rearms as 2, which is expected since it was rearmed with sysprep when capturing the image, so we know it was in fact rearmed).
    So my question is how and why did this happen? I was in a hurry so I just ran slmgr /rearm to burn off another rearm. I plan on putting in a KMS server at the end of the week, but I'm worried if I should redeploy the image to this machine since something
    appears to be wacky.
    Anyone seen this before or have any thoughts on the matter?

    Either way, it was correct when I checked it today so maybe it corrected itself after Windows was installed? Not sure how else to explain this one.
    Me either.
    After Windows is installed, if you are domain-joining, the clock will sync to your Domain Controller.
    If not domain-joined, Windows will try to sync to time.windows.com (or similar).
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Surface Pro MDT Install

    Have been struggling for a while to get a Surface Pro 3 to install using MDT, PXE boots OK but installation ends with an error relating to the unattend.xml file.  Looking at the setuperr log on the device the error is described thus:
    2015-03-05 07:53:52, Error                        [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-Shell-Setup, Language:
    neutral, ProcessorArchitecture: amd64, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/ComputerName
    2015-03-05 07:53:52, Error                        [setup.exe] SMI data results dump: Description = Value is invalid.
    Eventually worked out that this is related to the length of the serial number on the Surface Pro 3, we use the serial number in MDT to create the Computername.  as this must be 15 characters or less the use of the Surface Pro 3 serial number breaks
    this rule when we use our custom computername string WSERC%SerialNumber%, this had worked for ages as we've only installed Dell machines with a 6 digit service tag as the serial number.
    Fixed this using the following string WSERC#right("%SerialNumber%",10)#
    Surface Pro 3 now installs OK with MDT.

    Hi,
    Have you follow that guide to check key points?
    When you add the driver under Out-Of-Box Drivers for Surface pro, note the last folder must be called “Surface Pro”. If it's for Surface pro 2. it should be the "Surface Pro 2" folder name.   If your Out-Of-Box drivers contain drivers
    for other systems and you do not use one of the options in that guide. Then you cannot control what drivers get used during the deployment. This can lead to problems so we would recommend you use Selection Profiles or other methods to ensure only the drivers
    designed for the Surface are used during the deployment.
    For additional reading on this topic I encourage you to take a look at
    this blog.
    In addition, you also could consider to use a USB drive to update the firmware offline:
    How to Update the Surface Pro 3 Firmware Offline using a USB Drive
    http://blogs.technet.com/b/askpfeplat/archive/2014/10/20/how-to-update-the-surface-pro-3-firmware-offline-using-a-usb-drive.aspx
    Meanwhile, please use this article to troubleshoot missing drivers in MDT and upload the related log file here:
    https://social.technet.microsoft.com/Forums/en-US/3e083173-f5db-48e9-b744-f71b9ca6541c/how-to-debug-missing-drivers-in-mdt?forum=mdt
    Karen Hu
    TechNet Community Support

  • Surface Pro 3 Windows 8.1 Pro N HID Sensor Collection

    I've been tasked with creating an enterprise image on the surface pro 3. I'm using MDT 2013. I've added the driver pack to MDT for the surface pro 3.
    All drivers install except for HID Sensor collection device and the simple device orientation sensor.
    However, if I deploy my personal windows 8.1 pro image to the computer, it works fine.   Just not with 8.1 Pro N.
    In device manager it says error 10, cannot start device for the collection device.  The orientation sensor is not even listed.
    Any help would be appreciated.  All windows updates have been applied.

    The two files in use by "Simple Device Orientation Sensor" in Device Manager are: c:\windows\system32\drivers\umdf\sensorservicedriver.dll
    **I do not have this driver
    c:\windows\system32\drivers\wudfrd.sys
    **This driver is present
    There is also a "sensor monitoring service" service running. When disabled it breaks the ambient light and rotation sensor (probably other items too). At least that is a place to start. I can try and zip these to an email account if you like to
    see if it helps at all.
    **THIS WAS THE KEY** I found this in Services, and it was actually running, set to 'Manual.' I stopped the service and saw my screen brightness (assuming because it disabled the ambient light sensor) come on to full. I then changed it to Automatic, and restarted
    the service. After this I wishfully rotated my Y3P 90 degrees clockwise and the auto rotate did its job! I completely shut down the Y3P and booted up again... still working!
    I'm curious as to why it wasn't working even when the service was running, but not going to dwell on it now that everything is peachy.
    I really appreciate your time and help on an issue that diverged from the OP. I know this may break forum etiquette a bit but I was on a wild goose chase trying to find the solution. KUDOS! KUDOS FOR THIS MAN!!!

  • Brand new Surface Pro 3 with Office Prof Plus 2013

    Just purchased today and brought home a brand new Surface Pro 3.
    The first thing I needed for work, Office, and so I started to install, via USB DVD drive, the program Office Professional Plus 2013 - the fully loaded flagship version of Office that I purchased in March of 2014.
    I was shocked that I am unable to install it. I first tried installing the 64-Bit Office version, since Windows 8.1 is 64-bit. Next I learned that I must uninstall the 32-bit trial versions of Office that came pre-loaded onto the Surface Pro 3. I even used
    the Microsoft Office Fixit utilities and the Support descriptions of manual removal of previous versions of Office.Resetting the Surface Pro 3, uninstalling all Office products from it, and installing as 32-bit did not help either.
    The errors I see are not describable, because nothing happens, the install just hangs with no messages. The machine keeps operating fine, but the Office installs do not work at all.
    All of these efforts have only led to frustration.It appears to me that the flagship 2014 Surface Pro 3 and the Office Professional Plus 2013 (purchased only this Spring) are incompatible. This came as a great shock for me because in all my history of installing
    current MS software on current systems, I have never had this problem. Maybe back in the days of Windows 3.1 it might have happened. Please, if anyone has any advice , please advise.

    Thanks Melon Chen for your quick and helpful reply. Somehow (I will explain below), I was at last able to install the Office 2013 Pro Plus Suite.
    Before I received your reply with detailed instructions I kept trying many other solutions .. eventually I made Office 2013 Pro Plus install, although I'm not exactly sure what ended up fixing my ability to install from DVD.
    here's what I did:
    1) I attempted to install Office 2013 Pro Plus after running Fixit Utility and again the clean boot, but those did not help. I received the same error message that I described (ie. no specific error coded message, only a message that Office 2013 Pro
    Plus failed to install.  After rebooting with the "clean" reset option ,  I noticed there was some of my personal setup information retained on the system (can't recall exactly what this was , but it was clear to me that the reset
    did not make my system in pristine factory image). I discovered an even cleaner reset is the following to reset the Surface Pro 3 'absolutely' to factory image using a downloaded factory recovery image that is available here: 
    -->
    http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/downloadablerecoveryimage?lc=1033
    This also required creating a USB drive based install and this reset the Surface Pro 3 to factory condition as described here:
    -->
    https://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/usbrecovery
    Now, after all this, regarding the Office Pro Plus 2013 install, 64-bit, it failed yet again, but one good thing was that the error message stated something different ie containing the text
    " Background installation ran into a problem. ... We'll automatically resume...." . With this information, I explored the internet over the weekend and I found the following valuable site on the web:
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/unable-to-install-office-2013-error-codes-30102-1/fde35d75-bddc-4dd6-bd0a-e01d07420f49
    Although I did not observe the error codes (apparently, it is explained that MS has stopped showing many error codes) as depicted, but the symptoms were identical. And so reading the link, there was one user , Rohn007, who compiled a beautiful listing of this
    problem of installing Office 2013 Pro with suggested solutions; lo and behold, the solution describing
    multiple wireless devices seemed to solve the problem. In other words, by being a heavy MS early-adopter, during Office 2013 Pro Plus install, I had a couple of MS devices, like Lumia phone, pc, etc.. all linked to the same wireless router
    during my attempts to install to the Surface Pro 3.  I have only a single MSN user ID and password for all the devices. I could be wrong, but this situation with shared wireless apparently can mess up the installs of Office 2013 Pro Plus- but often it
    is disguised and murky because no error codes are generated. By turning off all the wireless connections except for the one connecting to the Surface Pro 3, I was AT LAST ABLE TO INSTALL OFFICE 2013. 
    In the end, I installed Office 2013 32 bit, but I really wanted 64 bit. I will try now and uninstall everything again. and then go for the 64 bit version.
    I was very worn out by this experience. A full 2 days trying to install a brand new Office 2013 onto the brand new Surface Pro 3 with Win 8.1 apparently all came down to the fact maybe that I had too many wireless connections going! In the end I am
    happy that I can finally discover this beautiful piece of hardware, but I am a bit scared since I also would like to install Adobe CS4 from DVD drive and I am worried that I will again have much trouble. Do you have any suggestions when installing the Adobe
    CS 4 Master Collection, are there suggested steps to take? I like the idea of running Event Viewer, do you think that cab be helpful during installs.

  • Issues with the Surface Pro 3's pen in Photoshop CS6

    I used photoshop CS6 with no problems on my old computer that was connected to a graphics tablet.
    However, I recently bought a new windows computer called the Surface Pro 3. Everything works perfectly with the trackpad and touch, but I've had some issues with the Surface pen.
    The pen can draw on the canvas, but whenever I click something on any of the windows with the pen, the entire application freezes and I would have to click the computer's taskbar at the bottom to unfreeze the application.
    It's impossible to work like this. Is there any solution to fix this problem? It says that the version of photoshop I have is Adobe Photoshop Version: 13.1.2

    If you have Photoshop CS6 version 13.1.2 which is the Subscription version of Photoshop,  You shoule  Isstall Photoshop CC 2014 on your surface Pro 3.  It will work without problems on the surface Pro 3 and you will also have the option have the option to use Photoshop CC 2014 preference 2x UI to scale Photoshop's UI up in size on your Surface Pro 3.
    If you do not have a subscription the Perpetual version of windows CS6 should be version 13.0.1.3.  In that case the only way to scale Photoshop UI is to have windows do it. You would need to to update your windows 8.1 registry and add an external Photoshop manifest file in your Photoshop CS6 folder.  To get the Surface Pro 3 pen to work with Photoshop you would need to install NTig pen device drivers the support the wintab APIs.
    You will not be able to use Photoshop without a keyboard popping up the windows onscreen keyboard is too cumbersome.  You can use a utility like Touchkey to create Overlay touch keys on Photoshop and use Photoshop without a keyboard.
    The differece betweek Adobe 2XUI scaling an windows scaling ise windows scaling scalet the image areas as well as the Photoshops UI
    A couple of touchkey overlat keyboards could look something like this

Maybe you are looking for