To reproduce:

1) Run Disk Management as a user that both:
- is a local admin, and
- has domain credentials to access some network share

2) "Attach VHD", choose a .vhdx file stored on a network share.

3) Run Disk Management as a user that both:
- is a local admin, and
- does not have domain credentials

4) Right-click the VHD's item in the Disk list, click "Detach VHD"

Observe that a dialog pops up reporting the UNC path to the VHD file, which is of course already a bad sign.
Click OK.
Observe that an dialog pops up reporting "The user name or password is incorrect."

Note: This command does still succeed if run as a user with domain credentials. So, it appears maybe the method of detaching was changed under the hood, and this usage scenario was not tested.

Hello,
I found a couple of issues with RDP work:
1) Applications sound transfer. Some Win10Pro PCs (only few of many similar ones) have issue with transfere of applications sound. I can hear system sound check, but I can't hear any applications: players, browsers, etc. All settings allowed and correct, other PCs transfere all sounds.
2) If I set all devices to transfer with RDP, transfered screen starts to freeze after some time of work. It happens every time. Screen stops updating, but RDP still works and I can click Remote Desktop, but i won't see what happens until I reconnect to PC with RDP.

legacy systems needs to go to cloud

.NET and Win32 softwares will be around for long time, for sure..

why container? 1nd

Large systems with decades of code written, composed by 3rd party components can not be changed right away. So containerizing monoliths, are one important step on the jorney to the cloud

why container? 2st

I'm newbie, but as far as I know, the whole thing about containers is ship it as image once and run it everywhere, with environment isolation and integrity.. right?!

the issue

There is no way to properly set globalization settings like Time Zone, Language, or Windows-Location on Server Core containers. Once I can not control the container host, I don't know where my software will run: Azure AKS, AWS, On-Prem, data centers, Windows Desktops,..
So, I need to ensure some container environment settings..

the feeling

I'm very sad.. Microsoft should realize that globalization settings like language and time zone are fundamental to keep the world running..

Otherwise, Windows Server on container is useless, and if you have an OS useless for containers, what do you have?!

I want to go to cloud, I want to go with Windows platform, please don't stop me...

more details and context

https://github.com/moby/moby/issues/40284

The Option "Stop task if it runs longer than" under Triggers no longer kills the running task in Server 2016/2019.

The same scheduled task that would be killed after the time set on the Trigger of the scheduled task in all Server version before Server 2012 R2 are not terminate on Server 2016/2019.

I confirmed this with creating a basic task to run notepad and kill it after a minute in Server 2019 and upon execution task scheduler never kills notepad.
This same job was exported to Server 2016 and it didn't work either. The XML was then imported to a Server 2012 R2 server and it did work, i.e. notepad was killed after 1 minute as specified on the Trigger.

I also tried the global setting on the scheduled task itself to stop the task but that didn't work either.

Hello,

on a fresh installed and fully patched Windows Server 2019 Std if I enable RDSH role the Windows Search stops working.

Windows Search service looks good and eventlog shows no errors but Indexing Options shows no locations enabled for indexing and I am unable to add them

Things I have already tried

1 - Windows Search service restart

2 - Server restart

3 - Rebuild Index

4 - Enable Windows Search feature

5 - DISM ad SFC

6 - Windows Troubleshoot - shows incorrect permission on C:\ProgramData\Microsoft\Search\Data folder but is unable to fix them. If I manually fix those permissions, search still not works adn permission are automatically reset to previous not working ones

Thank you in advance for help

UPDATE:

Uninstalling RDSH role fix the issue. Unfortunatelly I need both RDSH and Windows Search

BUG confirmed by other users here:

https://social.technet.microsoft.com/Forums/en-US/4c200f89-5905-42b3-ab27-0d7771c0ecb7/rdsh-role-breaks-windows-search?forum=ws2019&prof=required