Surface Pro 3 with MDT deployed 8.1 Enterprise integrated Update 1 missing power button?

I am building / deploying an image for Surface Pro 3. Out of the box the Surface Pro 3 has the power button on start screen next to search button. However when I deploy 8.1U1 Ent the button disappears. Reading
http://winsupersite.com/windows-8/windows-81-update-1-tip-toggle-power-button it appears depending on if the Surface Pro 3 is defined as Slate or Ultrabook it might or might not default to power button being on. Is this expected behavior, anyone else see
this?

Luckily I found
http://blogs.technet.com/b/askcore/archive/2014/07/15/deploy-windows-to-surface-pro-3-using-microsoft-deployment-toolkit.aspx which goes into more detail and has workarounds for deploying Surface 3.

Similar Messages

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

  • Cannot draw in Flash Pro CC on Surface Pro 3 with latest N-Trig drivers...Is there a current fix?

    Cant draw in flash pro cc on surface pro 3 with latest n-trig wintab drivers. Many others online say they have this issue on surface pro 3 also...Is there not some type of current fix. Someone on the adobe forums said the problem was fixed internally in flash pro and that the fix will come with next adobe flash pro update, but when is that?
    Flash updates don't exactly  come every month or even 2 months, and this issue needs some type of current fix because there are many ppl also having this issue, which basically makes Flash Pro useless, what good is an animation program if you cannot draw in it on a tablet that literally SPECIALIZES in pen/drawing usage. So anything out there ??

    bump
    its very frustrating as I'm paying monthly for CC and can't use one the programs I need for my design job! Looking at other programs.  

  • HT5945 new macbook pro loaded with mavericks. installed CS3 including prompted Java update. try to open photoshop &  empty splash screen pops up-can't go further. tried newer java update-same result. re-opened 4 times-same. help!!

    new macbook pro loaded with mavericks. installed CS3 including prompted Java update. try to open photoshop &  empty splash screen pops up-can't go further. tried newer java update-same result. shut down 4 times-same. any suggestions?

    Kappy wrote:
    Has it occurred to you that CS3 isn't compatible with Mavericks? Try using CS9 or 10.
    Sorry that's untrue. I have Photoshop CS3 running on 10.9.
    CS9 or 10? Now you are just making stuff up.
    Adobe claim CS3 will work, with a minor issue…
    http://helpx.adobe.com/x-productkb/global/mac-os-mavericks-compatability.html
    The Adobe updater fails to work for me.
    I was prompted to install J6RE which came from Apple, check the Apple support downloads http://support.apple.com/downloads/#java%206
    Sorry can't provide a direct link, it was just a dumb 'You need … please click install' dialog.
    I think the 10.9 java updater is installing version 7.

  • Yesterday for the first time i turned on my macpro 2011 model and i got a crazy gray screen with lines all over it ,so i held down the power button and turn off then restarted and all was ok could someone help me with this,what caused this shut down. werd

    yesterday for the first time i turned on my macpro 2011 model and i got a crazy gray screen with lines all over it ,so i held down the power button and turn off then restarted and all was ok could someone help me with this,what caused this shut down. werd

    Are the lines like psychedelic herringbone?  If yes, I had that happen once, it was something serious, like the
    Logic board. The good news is that it was fixed without any loss of data on the hard drive. Take it in to have Apple look at it ASAP.  I took it to TekServe at the time, they are very nice about preserving your data and user library when possible.
    Good luck and don't panic.

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

  • Wifi on Surface Pro - installed with ndiswrapper but not working

    Hi there guys.
    I have installed Arch on a Surface Pro and most things work well.
    The biggest problem so far is wifi - it comes with a 88w8797 Marvell Avastar chipset. I managed to find the drivers and used ndiswrapper to install them.
    $ ndiswrapper -l
    mwlu97w8 : driver installed
    device (1286:2043) present (alternate driver: mwifiex_usb)
    The ndiswrapper help page says that one should get rid of alternate drivers before enabling ndiswrapper but I have no clue where to start - that seems to be a kernel loaded module (link) but it really doesn't do much apparently.
    I did 'modprobe ndiswrapper' but as you can see below, nothing seems to be really happening
    # iwconfig
    enp0s20u2u3 no wireless extensions.
    lo no wireless extensions.
    dmesg returns this on ndiswrapper
    $ dmesg | grep ndiswrapper
    [ 2.996565] ndiswrapper version 1.58 loaded (smp=yes, preempt=yes)
    [ 4.230024] usbcore: registered new interface driver ndiswrapper
    The gnome network manager, just like iwconfig, shows no able wireless.
    I'm at a loss on what to do, any help is greatly appreciatted
    Last edited by OttoRobba (2013-02-21 10:26:50)

    The blacklisting was a good call as I had completely forgot to do so. Made a /etc/modprobe.d/blacklist.conf  with 'install mwifiex_usb /bin/false' -  nothing changed though, the wireless network still won't show.
    # lsusb
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 003 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub
    Bus 003 Device 002: ID 1286:2043 Marvell Semiconductor, Inc.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 045e:0795 Microsoft Corp.
    Bus 002 Device 003: ID 045e:079c Microsoft Corp.
    Bus 002 Device 004: ID 03eb:8209 Atmel Corp.
    Bus 002 Device 005: ID 045e:0794 Microsoft Corp.
    Bus 003 Device 006: ID 04e8:6863 Samsung Electronics Co., Ltd
    # lspci
    00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
    It seems ndiswrapper is failing to load - I wonder if there is another module claiming the device?
    #dmesg
    [ 4.191249] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'__chkstk'
    [ 4.191274] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
    [ 4.191295] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
    [ 4.191305] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
    [ 4.191326] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeMdl'
    [ 4.191336] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
    [ 4.191346] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
    [ 4.191356] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
    [ 4.191366] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
    [ 4.191376] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
    [ 4.191386] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMAllocatePort'
    [ 4.191403] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationComplete'
    [ 4.191413] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationConfirm'
    [ 4.191423] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMFreePort'
    [ 4.191432] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMNetPnPEvent'
    [ 4.191443] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
    [ 4.191453] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
    [ 4.191463] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
    [ 4.191473] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
    [ 4.191483] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSetMiniportAttributes'
    [ 4.191493] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetOptionalHandlers'
    [ 4.191504] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
    [ 4.191514] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
    [ 4.191523] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeTimerObject'
    [ 4.191533] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisCancelTimerObject'
    [ 4.191543] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetTimerObject'
    [ 4.191599] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
    [ 4.191613] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterMiniportDriver'
    [ 4.191623] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
    [ 4.191648] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateTimerObject'
    [ 4.191663] ndiswrapper (load_sys_files:199): couldn't prepare driver 'mwlu97w8'
    [ 4.191827] ndiswrapper (load_wrap_driver:121): couldn't load driver 'mwlu97w8'
    [ 4.191926] usbcore: registered new interface driver ndiswrapper

  • Surface Pro 3 with Illustrator CS6/CS3

    Hi there,
    before I want to buy the Surface pro 3 I have a few questions. The main reason I want to use it for is to work with Adobe Illustrator.
    1) I've installed CS6 student edition on my desktop pc at the moment. Is it possible to use CS6 student also at the Surface by using the same license as on the pc.
    2) Can I use the pressure sensative of the brushes in Illustrator CS6 with the Surface 3 pen?
    3) If it's not possible to use CS6 on both devices, I have also the older Illustrator CS3 student edition. Has anyone tried to use this pressure option in the Illustrator CS3 on the Surface pro 3?
    4) Could you generally advise to use Illustrator on the Surface pro 3. I've read that the GUI symbols are very small. Has anyone experiences?
    Thank you so much,
    ktoffler

    You shouldn't have much problems with the surface. The only thing I can think of is the issue of the higher resolution. Since illustrator is an older version is is lacking the features for higher resolution monitors. You may need to lower the resolution to make it easier to see and use. Other than that you should be fine.

  • Surface pro 3 with illustrator (2014) update.

    I was curious if anyone has made the plunge on the new surface pro 3 and had any time with the new Illustrator update (2014)? Does the UI scale? wintab driver issues? Color reproduction accuracy? I'd love to hear some feedback from the illustrator community on this. I've only found one youtube video on this topic. If you want to see it

    You shouldn't have much problems with the surface. The only thing I can think of is the issue of the higher resolution. Since illustrator is an older version is is lacking the features for higher resolution monitors. You may need to lower the resolution to make it easier to see and use. Other than that you should be fine.

  • Surface Pro 3 with AIR-AP1042N-N-K9 Wireless Access Point

    I am trying to connect two recently purchased Microsoft Surface Pro 3 windows 8.1 tablets to a cisco AIR-AP1042N-N-K9 (firmware 15.2(4)JA1) wireless access point. The tablet asks for the wlan password then displays 'can't connect to network'. I am able to connect to the AP using other Win 8.1 devices using WPA2-Personal + TKIP. The Surface Pro 3s connect to other wlans using other access points.
    Please would you help.

    Thank you man that *REALLY* worked!
    Regards,
    Stefano.
    pcroak ha scritto:Stefano,The 521 series AP can operate in lightweight or standalone mode. If your AP currently has the lightweight image on it we can convert it using tftp. (I suspect it does, as the part number AIR-LAP indicates lightweight while AIR-AP is typically standalone)The best way to confirm is to check the cdp neighbor details for the AP software version (or login to the AP console and issue a "show version").If the software has "k9w7" in the name, that is standalone. If it has "k9w8" then it is lightweight. When operating in lightweight you will not be able to telnet/ssh or go to the AP web page.To convert your AP to standalone, please follow the procedure found here:http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp160918-Patrick CroakWireless TAC

  • Download free trial Illustrator.  windows surface pro 3 window 8.1.  cloud says app updated.  illustrator will not open

    Hello,
    I downloaded the free 30 day trial of Adobe Illustrator on my Surface Pro 3.  The download process has seemed to go okay, the app says it is updated.  When I go to open it, cursor spins for a second but nothing happens.
    Thanks

    Macdog,
    You may try this specialized forum (where you may be able find the answer from previous threads),
    http://forums.adobe.com/community/download_install_setup
    or
    Creative Cloud support (all Creative Cloud customer service issues)
    http://helpx.adobe.com/x-productkb/global/service-ccm.html

  • My Mac book pro can't start totally despite repeated attempt to off /on the power button , anybody there can help me ?

    Hi,
    My Mac book pro , 13 " which I bought in late 2011 , iOS 6 system, today suddenly can't start at all after I try to sync with my iPhone . Anybody there can help me urgently .?....I have tried repeatedly to switch off and then switch on the power button , but to no avail .... I really don't know what is going on ? So far , it never give this type of problem.
    Thanks for anybody who can help me in this .
    Rgds,
    Daniel

    1. Your MacBook Pro does not run iOS 6 system. iOS is for iPhone, iPad devices. From the Finder menu select the Apple>About This Mac should give you the operating system you are running. So now what happens when you push the power button?

  • Macbook air locks up instead of standby. Cannot wake with screen black and no sound. Have to hold power button for total restart. Happened with Mountain Lion and Maverick

    I've had this issue since first buying my MBA mid-2013. Instead of going to standby, which works 98% of the time, every now and again it appears to go into standby with the screen black, but no amount of key pressing or mouse moving will wake it up. I am forced to hold down power button for a manual restart and faced with losing work. This problem has occured whilst using Mountain Lion and still occuring since updating to Maverick.

    GoreLeech wrote:
    Hello,
    Having searched high and low, I can't seem to find a solution to my predicament.
    Sun Feb 13 20:50:44 2011
    panic(cpu 0 caller 0x9f8bfa): NVRM[0/1:0:0]: Read Error 0x00000100:
    Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB
    Hi there, GoreLeech,
    as per above extract from your error log, you have experienced a kernel panic due to problems with your Nvidea GeForce GT 330 M graphics card that has a 256 MB memory.
    This may be due to the card not having enough memory for what you are doing, the only thing, I can suggest here is to call Apple, and get the machine checked out. You can run the Apple hardware test at home but I'd recommend getting it booked in with Apple. What is worse: A computer that randomly malfunctions, or doing without it for up to one week (often they repair it within a day!)?

  • My MacBook pro is frozen and I can't restart, even by using the power button or control command

    Hi- my MacBook pro froze about an hour ago and I've been unable to reboot it. Any suggestions? I've tried the power button, control + command + restart, erc ad none of them do anything.

    Hold down the power button for 6-7 seconds.  It will power off, then click the power button to turn on again.
    Regards,
    Captfred

  • My macbook shows a only white screen with apple logo and spinning wheel when i on the power button? How can i correct that?

    Any help!!!

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
         a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
    Step 6
    Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 7
    Repeat Step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
    Step 8
    This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. Both desktop and portable Macs used to have such a battery. The logic-board battery is separate from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 9
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested. If you can't get to an Apple Store, go to another authorized service provider.

Maybe you are looking for