TomWheel

Q: Windows 10 Fails To Shut Down my Late 2013 Mac Pro

I upgraded Windows 8.1 installed under Bootcamp  on my Late 2013 Mac Pro to Windows 10 and installed the latest Bootcamp support software for Windows 10 recently provided by Apple.  Both the upgrade and the installation of the Bootcamp support software occurred with no errors and both went fully to completion.  Windows 10 runs fine on my Late 2013 Mac Pro and all is well until I try to either shut down or restart this Mac Pro.  When I select Shutdown or restart in Windows 10 all of my external drives and other USB devices shut down properly and my monitor turns off as it should.  However, my Late 2013 Mac Pro remains on as indicated by yhe white power light on the rear remaining lighted and I have to press and hold the power button for about 10 seconds to turn off the computer, and then press it again to restart in OS X.  This occurs only when trying to restart or shutdown in Windows 10.  When I am using OS X, I have no problems restarting or shutting down this system.  I also have Windows 10 running under Parallels 10 and I have no problem in Parallels shutting down or restarting Windows 10.  The failure to shutdown properly only occurs when running Windows 10 via Bootcamp.

 

I would be most appreciative of any help that you can provide to me, and I thank you in advance for your help.

 

Tom

Mac Pro, OS X Yosemite (10.10.5), 1 TB PCIe Flash, W700, 64 GB ram

Posted on Aug 14, 2015 7:27 PM

Close

Q: Windows 10 Fails To Shut Down my Late 2013 Mac Pro

  • All replies
  • Helpful answers

Previous Page 2 of 3 last Next
  • by nazaire,

    nazaire nazaire Aug 23, 2015 9:53 PM in response to TomWheel
    Level 1 (0 points)
    Aug 23, 2015 9:53 PM in response to TomWheel

    Tom,

    Same here, 8 cores, D 700,

    The problem seems to be when you upgrade to Windows 10, as Microsoft has opted for a compulsory update download and automatic install of all softwares updates, they feel should be on your machine,

    The glitches appears on the apple machine as AMD Driver Auto detect seems to think as you have a D700 and Windows 10 it needs to install the latest (June 15) AMD Driver made for a Windows computer, when this driver install in the background without you knowing it, the troubles start,

    However if you are patient and wait 30 minutes or so the program shut down by itself,

    Here is a solution that work for me: went to the AMD website, Drivers Download page, then download on your window side (Bootcamp C) the driver made specially for Apple BootCamp this is an older one (December 13 0r so) then open and instead of install click on remove all AMD drivers from this computer, after this is finished use you USB fat 32 to reinstall BootCamp 6 from Apple it will say repair BootCamp click and voila back to normal

    But this problem is bound to happen again to stop it:

    Read: https:// support.microsoft.com/en-us/kb/3073930

    How to temporarily prevent a Windows or driver update from reinstalling in Windows 10

    You have to download a program that allow to do this:  " wushowhide.diagcab"     launch and follow instructions it allows you to stop the updates you don't want to install and  prevent any AMD drivers to install themselves automatically, the only AMD drivers that work with Apple hardware and Windows 10 are from BootCamp 6, the old AMD drivers  made specially for Apple BootCamp work well with Windows 8.1

    This is how I solved the 30 minutes hangup, but others solutions may work better when all the bugs are ironed out.

    Naz,

  • by battersea_puppy,

    battersea_puppy battersea_puppy Aug 24, 2015 1:13 AM in response to nazaire
    Level 1 (4 points)
    Windows Software
    Aug 24, 2015 1:13 AM in response to nazaire

    Stop posting nonsense. I did clean Windows 10 install and clean Bootcamp 10 install and DID NOT automatically update drivers from MS update and it doesn't work. What regards to colour depth settings another nonsense.

  • by brianrogers,

    brianrogers brianrogers Aug 27, 2015 2:14 AM in response to TomWheel
    Level 1 (10 points)
    Aug 27, 2015 2:14 AM in response to TomWheel

    Anyone use Bootcamp 6 Driver for Windows 8.1 can confirm this problems has not happened ?

     

  • by yassie2,

    yassie2 yassie2 Aug 27, 2015 11:42 PM in response to brianrogers
    Level 1 (0 points)
    Aug 27, 2015 11:42 PM in response to brianrogers

    I installed Windows 8.1 pro with Bootcamp 6. This problem doesn't happen.

  • by Rolfilein,

    Rolfilein Rolfilein Sep 3, 2015 3:33 AM in response to [maven]
    Level 1 (0 points)
    Sep 3, 2015 3:33 AM in response to [maven]

    Hi Maven,

     

    did you get further with your problem? I'm stuck as you described... horrible for bootcamp to cut power by half.

     

    Anyone maybe get the new 15.8 driver into windows 10 or some kind of modding like in windows 8.1?

  • by hackintosh5,

    hackintosh5 hackintosh5 Sep 3, 2015 9:07 PM in response to TomWheel
    Level 1 (0 points)
    Sep 3, 2015 9:07 PM in response to TomWheel

    I think I found the true problem it's Windows 10 hibernation it self. I found Windows user groups having similar issue.

    The fix is to disable the hibernation. I tried it and worked for them the couple times I had to restart or shutdown.

    Open command prompt as Administrator then type the command below and enter.

    powercfg -h off


    Cheers and enjoy.

  • by battersea_puppy,

    battersea_puppy battersea_puppy Sep 4, 2015 12:04 AM in response to hackintosh5
    Level 1 (4 points)
    Windows Software
    Sep 4, 2015 12:04 AM in response to hackintosh5

    Yet another nonsense post about hibernation. I switched off hibernation after install and it didn't made any difference. As I mentioned before stop posting nonsense!

  • by jmoye,

    jmoye jmoye Sep 4, 2015 6:25 AM in response to hackintosh5
    Level 1 (10 points)
    Sep 4, 2015 6:25 AM in response to hackintosh5

    Did not work for me.  The only way I can get it to shut down is to turn off cross fire.

  • by battersea_puppy,

    battersea_puppy battersea_puppy Sep 4, 2015 6:32 AM in response to jmoye
    Level 1 (4 points)
    Windows Software
    Sep 4, 2015 6:32 AM in response to jmoye

    Of course it didn't work and it won't work until Apple/AMD will provide proper Windows 10 driver written specifically for this graphic card but it won't happen - all they care about now is iPhone/Facebook users. We, hi-end product users are small minority so why bother.

  • by hackintosh5,

    hackintosh5 hackintosh5 Sep 4, 2015 7:16 PM in response to battersea_puppy
    Level 1 (0 points)
    Sep 4, 2015 7:16 PM in response to battersea_puppy

    Yes you are nonsene, impolite, and naive.  So much for trying to help people if this what you get back from them.

  • by battersea_puppy,

    battersea_puppy battersea_puppy Sep 5, 2015 1:00 AM in response to hackintosh5
    Level 1 (4 points)
    Windows Software
    Sep 5, 2015 1:00 AM in response to hackintosh5

    Go help somewhere else.

  • by fbis,

    fbis fbis Nov 14, 2015 1:10 PM in response to TomWheel
    Level 1 (0 points)
    Nov 14, 2015 1:10 PM in response to TomWheel

    hi there

     

    with the windows 10 update 1511 (Build-Nummer 10586) this issue is solved.

    my mac pro late 2013 reboot, shutdown and sleep work as expected.

     

    cheers

  • by BadLeopard,

    BadLeopard BadLeopard Nov 28, 2015 8:24 AM in response to TomWheel
    Level 1 (0 points)
    Nov 28, 2015 8:24 AM in response to TomWheel

    My late 2013 Mac Pro still has this issue after the 1511 update. Turning off crossfire does alleviate the problem, so that's a plus. Thanks to brianrogers for that fix!

     

    I really don't see it as that big of a problem, since you can just leave crossfire turned off until you need it. As far as I know, the only time crossfire comes into play is while playing games that support it in full screen, and possibly rendering from Adobe Premiere Pro. Other than that, you're just using one card anyway.

  • by battersea_puppy,

    battersea_puppy battersea_puppy Nov 29, 2015 2:39 AM in response to BadLeopard
    Level 1 (4 points)
    Windows Software
    Nov 29, 2015 2:39 AM in response to BadLeopard

    I can confirm that all Windows issues affecting Mac Pro (late 2013) AMD graphic drivers at last are solved after over 1 year of constant problems.

    Here is procedure you need to follow:

    1. If you use Logitech Set Point uninstall it.

    2. Run Apple Software Update wizard - there was recent Bootcamp update and update your Bootcamp

    3. If you will need to use Logitech Set Point use old version 6.32.7 ONLY! Latest version cause screen flickering and AMD Driver Not Responding error message.

     

    Reboot and shut down works perfectly now and "AMD driver not responding" error is gone.

  • by BadLeopard,

    BadLeopard BadLeopard Nov 29, 2015 3:46 AM in response to battersea_puppy
    Level 1 (0 points)
    Nov 29, 2015 3:46 AM in response to battersea_puppy

    Yeah, I don't use Logitech Set Point and am not getting error messages. Sounds like you were having a different issue than what this thread describes.

Previous Page 2 of 3 last Next