none
Domain-joined Windows 10 won't start RRS feed

  • Question

  • Today I have 4th case where domain-joined Windows 10 won't start.
    It stops on black screen with dotted circle cursor (this screen shows up after Win logo).

    Environment:
    - domain: Windows Server 2018
    - clients (physical and VM as well): Windows 10 Education, 64-bit versions, latest updates

    Analysis:
    - workgroup Win 10 computers start up normally
    - repair does not help
    - no errors or warnings in Event Viewer
    - no hardware errors, no bad sectors
    - no BT keyboards or mice - it happens with VMs also
    - Windows 7 domain-joined computers start up normally
    - not aware a GP setting which would cause my problem



    • Edited by marianh Thursday, September 28, 2017 9:41 AM
    Thursday, September 28, 2017 8:32 AM

Answers

  • According to your description, I suppose that it may be caused by GPO.

    I narrowed it down to GP computer settings related to the Windows Store.
    I've configured them to 'Not Configured' (they were enabled):

    • Disable all apps from Windows Store
    • Turn off the Store application

    Also I found this error (which was logged as informational type of event!) in client's logs:

    Application popup: dwm.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application.

    However that error never showed up on startup screen.

    Edit: it turned out that Bypass traverse checking has also impact on starting up.
    In my case it was configured that specific group had permission to bypass...
    After switching it to Not configured Windows 10 starts up normally.



    • Marked as answer by marianh Monday, October 2, 2017 12:24 PM
    • Edited by marianh Thursday, October 5, 2017 6:51 AM
    Monday, October 2, 2017 12:24 PM

All replies

  • Domain joined PCs are fine with my domains in Windows 10.

    So can your create and OU deny all GPO to that OU, put a newly built Windows 10 machine into that OU (whilst adding it to the domain after its computer account is deleting but before the after domain added reboot happens) and does that boot?

    Thursday, September 28, 2017 9:59 PM
  • Hi marianh,

    According to your description, I suppose that it may be caused by GPO.

    If only 4 PC has the issue in domain environment, create a new OU, join this OU with domain accounts and computers that are not available, use the default GPO, and stop policy inheritance to check.

    Hope it will be helpful to you


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 29, 2017 7:38 AM
    Moderator
  • According to your description, I suppose that it may be caused by GPO.

    I narrowed it down to GP computer settings related to the Windows Store.
    I've configured them to 'Not Configured' (they were enabled):

    • Disable all apps from Windows Store
    • Turn off the Store application

    Also I found this error (which was logged as informational type of event!) in client's logs:

    Application popup: dwm.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application.

    However that error never showed up on startup screen.

    Edit: it turned out that Bypass traverse checking has also impact on starting up.
    In my case it was configured that specific group had permission to bypass...
    After switching it to Not configured Windows 10 starts up normally.



    • Marked as answer by marianh Monday, October 2, 2017 12:24 PM
    • Edited by marianh Thursday, October 5, 2017 6:51 AM
    Monday, October 2, 2017 12:24 PM