#StackBounty: #windows-10 #lock Locking applications z-order on Windows 10

Bounty: 100

Is there a way to lock the ordering of multiple windows even if one is focused?

I have six windows in which I only need to interact with the right edge and would like the layering to be preserved during interaction.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!

#StackBounty: #group-policy #windows-10 #mappeddrive Creators Update Stops Cross Domain GPO Drive mapping working ('0x80090005 Bad …

Bounty: 100

We’re testing out Windows 10 Creators Update (Build 15063) here. So far this is the only unsolvable issue we’ve encountered.

This issue is exclusive to Creators: identical Users and GPO’s work fine on Windows 10 Anniversary (Build 14393), and Windows 7 SP1, all with the latest windows updates run

We have two domains here, with no trust relationship between them. To get one particular drive mapped, we add the username and password in using group policy preferences (Used to be done with a login script, but changed to support user account control) to cross authenticate. Here’s a (redacted) screenshot of the preference options in GPO:

M Drive Error

When the policy runs on 10 Creators, the other’s drive map, but the M: Drive is not there. Looking at the event viewer gives this error:

The user ‘M:’ preference item in the ‘GPO Drive mappings {C65A2351-20C1-42D4-BF2B-AE604CD9DC0A}’ Group Policy Object did not apply because it failed with error code ‘0x80090005 Bad Data.’ This error was suppressed.

Error 4098

The user can manually map the same drive, adding the other domain’s credentials when prompted. They can also do it using the net use command.

I’ve tried googleing around GPO Mapping, Windows 10 Creators, and 0x80090005 Bad Data, but not found anything relevant.


Get this bounty!!!