Surface Pro Installation

Hello all and it's good to be back. I haven't used Arch in a few years or linux for that fact as everything at work required OSX or Windows. Things have changed and I've been able to switch back to Linux. I've been running Ubuntu on my Surface Pro (kinda) but miss the streamlined Arch distro. So I've been doing a little research and last night decided to pull the trigger. I made a bootable SD card image and booted the image. I made it through setting up the wireless (I thought). Set up the partitions and entered the
pacstrap -i /mnt base command
I get a screen full of error: failed retrieving file ....
ip link show mlan0
returns
mlan0: <BROADCAST,MULTICAST,UP,LOWER,UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
ping -c 3 www.google.com
ping: unknown host www.google.com
I had read in a thread somewhere that they feel the Marvell wifi was loading but not fully. I can use wifi-menu and see the wireless networks and choose one. I do have the latest firmware from Marvell (usb8797_uapsta.bin) but I don't know how to load it for the live image. So I would like to use this thread to address all the surface pro issues for installation with hopes of eventually creating a surface pro install wiki. To address later down the road, my power cover doesn't work as a keyboard. It works in the boot menu from the SD card but not once the image loads. I've just been using my Apple usb keyboard. Also I have a Netgear WMA1000M usb wifi adapter but that doesn't even show up in iw dev. Granted that is connected to the USB hub built into the Apple keyboard and lsusb does see booth the hub and the WMA1000M. So any help would be greatly appreciated.
Last edited by decaren (2014-04-13 17:54:19)

I made it through install this morning.  I'm running KDE and so far so good.  I'm no further with hardware then I was a couple of days ago.  I've pretty much spent all day trying to figure out where I go from here.  I still have no keyboard and worst of all I have no wifi again.  Now that I'm booting into KDE I'm using NetworkManager instead of dhcpcd.  But of course NetworkManager scans pretty much the first thing it does.  So back to the original issues, if the card scans it no longer will connect to the wifi.  I could work around this if I only connected to one network.  Unfortunately I will be connecting to no less than 12 networks with work depending on which of the 12 locations I am working at that day.  So does anyone have any idea on this one? 
On another note, still no power cover keyboard.  I don't care as much about the trackpad (I actually turn it off in Windows) because the touch screen worked out of the box and after installing Bluez 5.17 the Arc Mouse Surface Edition works as well.  I could only find one topic on the forum about the surface keyboard covers and it pointed to an Ubuntu forum topic.  I read through that and was stopped at one section for seeing the input. 
# cat /dev/hidrawX
That should have allowed me to see the input from what I understand but nothing.  I had one that had my current keyboard.  I'm thoroughly confused on that issue as well. 
Other than that everything else seems to be working for the most part.  Bluetooth is a little sketchy coming out of sleep and pen input doesn't work which I was never excited about anyway.  But the keyboard and wifi are my biggest issues.  It looks funny carrying a surface with a separate USB keyboard and having to save files and boot into Windows to send them sucks.  I have to do the same thing with OSX, but at least if I could get a working keyboard in all the OS's I could use a USB wifi dongle for a while.  The keyboard does work in OSX though.

Similar Messages

  • I own and am downloading CS6 for install on a new surface Pro 3 tablet, don't have or want the extended version, but the installer keeps wanting to install the extended version. My regist shows it as Photoshop 13

    I own and am downloading CS6 for install on a new surface Pro 3 tablet, don't have or want the extended version, but the installer keeps wanting to install the extended version. My regist shows it as Photoshop 13

    Thanks for your help Jeff. When I put serial# in, it won't except it.... I think it wants to see a previous version in my pc because my serial is for an upgrade, but when it put in a serial# for version cs5 it still wont except. Do you think i have to install cs5 first (which is also an upgrade).. which will require that I put in version cs4 etc,.etc., etc.
    Do you know how I can get into an chat with Adobe.Thats what i had to do last time I installed CS6 in my desktop PC.
    Thanks / Ron

  • Acrobat XI installation error Invalid Drive on surface pro

    cannot install acrobat XI Pro on Surface Pro, get error invalid drive D. I did mount SD card into C drive.  How do I install?

    are you installing on the default c drive?

  • How do I install itunes on a surface pro 2 tablet?

    My ipad won't update through the ipad so I need to do it through my computer but all I have is a surface pro 2 windows tablet and I cant install iTunes on it. Is there anyway to download it for my computer or other ways of updating ipads if it wont work on the ipad??

    iTunes should install on a Surface Pro 2 just like any other PC running Windows 8.1.  If you go to http://www.apple.com/itunes/ and click the Download iTunes button the next page should give you access to the appropriate installer.  Note, though, that the relatively limited storage, especially on the lower spec models, may limit the size of library you can have without using external storage.  iTunes itself requires 400Mb of free disc space to be installed.
    iTunes does not run on the original Surface and the Surface 2 that run Windows RT.  The new Surface 3 runs full Windows 8.1 and should support iTunes just like the Pro 2 and Pro 3.

  • Adobe CC on Microsoft Surface Pro

    I've installed Creative Cloud on my Surface Pro, and the apps I use tend to work fine - however, there's an issue with the Creative Cloud launcher itself.
    The CC context menu (right-click in system tray) only displays text for the first option in the list; the other options are present and can be selected, but have no text.
    Additionally, when the launcher needs an update, a small popup appears over the launcher app window. The content for this popup is not correctly displayed; only the CC logo is visible, there are no text or buttons, and the popup's 'close' button (top-right of popup) cannot be clicked. I'm *guessing* that this is an update dialogue, as it went away after I manually updated the launcher app (by re-running the installer).
    Both of these issues could be related to a known font sizing bug, but I've set my dektop to 100% zoom (native pixel sizing) so I wouldn't have thought that would be the problem.
    I've updated my Surface to Windows 8.1 - could that be the issue?

    Hi Dave,
    I'm afraid I didn't install Creative Cloud before upgrading the Surface to Windows 8.1, so I don't know if the issue occurs with the standard OS that the Surface Pro ships with (and it's not easy or practical for me to roll back at this stage).
    It *could* just be a strange configuration issue with my machine, but it's probably worth the developers exploring further as 8.1 will be leaving preview and shipping fairly soon; if it's a reproducible error you may see it cropping up a fair amount.

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

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

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

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

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

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

  • Installing Creative Design Suite Standard on Microsoft Surface Pro 3

    I am trying to install the Creative Design Suite on a Microsoft Surface Pro 3 from a DVD (I recently changed computers and need to transfer my programs to the new machine.  From my research assumed the Surface would work well for my needs and allow me to dabble in Illustrator and Photoshop as I learn the programs).  I am using an external optical drive however the single USB port on the Surface does not seem to get enough power to run the full installation.  I can get the installation started and go so far as to put my in my serial number and then it stops working.  At one point I was even given the notice that it appears my software is counterfeit - which it is not.  I legally purchased it and have used the same disk on another machine.  Is there a way to install the software that would allow me to bypass the usb port/optical drive situation?  One solution I read was to use the disk to transfer the program files to another machine, put them on a jump drive and then run installation on the surface through that - but I don't think I can do that with the serial number situation.  Has anyone else encountered this problem?  Ideas? 
    -I know the smart thing to do would be to upgrade to the cloud, however at this time I am not proficient enough in the programs that I want to pay $20-30 a month for the programs I am trying to learn.  The disk software I currently own is for CS6 and was purchased just before Adobe started using the cloud feature for their programs. 

    What issue do you have with downloading the installation files?
    CS3 - http://helpx.adobe.com/creative-suite/kb/cs3-product-downloads.html
    CS4 - http://helpx.adobe.com/creative-suite/kb/cs4-product-downloads.html
    CS5 - http://helpx.adobe.com/creative-suite/kb/cs5-product-downloads.html
    CS5.5 - http://helpx.adobe.com/creative-suite/kb/cs5-5-product-downloads.html
    CS6 - http://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html

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

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

  • Trying to download and install Photoshop Elements and Premium on Surface Pro 3 from the link and receiving an error - anyone know of a resolution?

    I have a Surface Pro 3 and just purchased the download link for Photoshop Elements (newest one) from Adobe. I've tried downloading several times and in 64 and 32 bit types, but have only made it as far as the install before receiving an error. Anyone else have this problem and know of a solution?

    Hi Jeff -
    I tried chatting with someone earlier today, but they ended the session (I think accidentally?) before it was resolved. My error is below. Now chat seems to be closed - although I thought it was open 24/7, so I can't try that again. This is the most frustrating support experience I've ever had. I just want to access and start using the products I purchased Friday. I would be so happy if someone would just help fix this. I am not computer inept, but cannot figure out why the download is failing.
    The guy on chat that was helping me before getting cut off had me run a SCANNOW system scan, but that's where the session unexpectedly ended.
    Exit Code: 7
    Please see specific errors below for troubleshooting. For example,  ERROR:
    -------------------------------------- Summary --------------------------------------
    - 0 fatal error(s), 2 error(s)
    ERROR: This installer does not support installation on a 64-Bit Windows operating system. Please download the 64-Bit version of Photoshop Elements.
    ERROR: System check returned with error : 6

  • 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

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

  • Trouble with deploying Win 8.1 and Office 2013 to Surface Pro 2

    Setup; Win2012R2, WDS 6.3.9600.16384, MDT 2013 (6.2.5019.0), Surface Pro 2 128GB, MS USB Ethernet adapter
    Issue 1: the TFTP transfer of the PE image is Extremely slow. 10 Mbps. Have tried to adjust Maximum Block Size without any improvement.
    Issue 2: When I try to deploy both Windows 8.1 and Office 2013 the TS fails. It will not (start) installing the Application - the log confirms that it starts the script, but ends up with ZTI Heartbeat forever.
    If I install Windows first and after the OS installation connect to the MDT server and start a TS With just Office 2013 it works without problem.
    The disturbing part here is that if I use the same TS With both OS and Office on a Hyper-V Virtual machine it works...
    Have anyone seen this before?

    Hi,
    I test in my environment, and Windows would finish the index, the CPU usage keeps in 29%, which my RAM is 8G.
    Can you tell us how you let the Windows Index run?
    Alex Zhao
    TechNet Community Support

  • TWO Questions Before Signing Up - Surface Pro 3 + license related

    I currently have CS6 and tested it on my Surface Pro 3 and the UI is so TINY its nearly usable. In everything I have read it appears the issue is on Adobe's end for not supporting windows higher resolutions or the calling to scale. Is there a known fix for this I am not seeing in the community?  If I buy a license for Photoshop CC will it have the same scaling issues and micro sized user interface as CS6?
    Question two is related to the license I purchase.  Can I have the program on my desktop as well as my surface with a single license?   Look forward to hearing back from someone, thanks in advance.

    HiDPI and retina display support FAQ
    One license entitles to two installations – though I’m not sure anymore if that’s for non-simultaneous use or is that condition has been dropped.

Maybe you are looking for

  • How do I delete/hide songs from iTunes Match? (More info inside)

    How do I delete/hide songs from iTunes Match? When I mark them, and delete them (and yes, I mark the box where it says delete from the cloud as well), they just reappear once I sync with itunes match again. (the symbol available for download appears)

  • How to get the field names of a table

    hi all, i need to get all field names of a table. here i dont need any data. i need only field names. initially i used this query, select * from tname; the problem is if table have 1000 records, all records will be in memory. how to get this one. reg

  • Web Photo Album 2.1 - putting it in page

    Hi, I'm on DW MX and haven't used it in a while. I installed the extension web photo album 2.1 and I have a page onto which I want to put a photo gallery. So I have the page created and my cursor placed and I chose 'Command/Create Web Album2.1" and I

  • Issue with compounding characteristics in the query

    Hello guyz I have an issue with 2 chars one compounding the other in the query. The 2 chars are : Action Type and Action Reason in HR. Action type is the compounding char. for action reason. For example: we have Action Type    Action Reason 01       

  • Error: Unparseable date with OracleXMLSave

    Hi, Error: oracle.xml.sql.OracleXMLSQLException: java.text.ParseException: Unparseable date: "03/18/2099" int oracle.xml.sql.dml.OracleXMLSave.insertXML(org.w3c.dom.Document) void b2b.RcvQueueListener.saveCsmToTso(oracle.xml.parser.v2.XMLDocument) vo