Hi

We have 8 RDS server, all running Windows server 2016, but after installation of Windows server 2016 update KB4593226, Microsoft print to PDF is not working anymore

When I try to print an document to PDF printer, the printer dialog box says following "Before you can print, you need to sect a printer"

I have try to uninstall the "Microsoft print to PDF" and install it again, but when I try to install it again I get following dialogbox from "Network
printer installation wizard"
Printer driver was not installed

The system cannot find the file specified
It look like Windows doesn't now where to find printer driver after installation of December 2020 update KB45933226

When I uninstall KB45933226, everything is working again, please help ?

/Jan

The problem is that server backup will only show a status of set up/configured after running a successful backup despite "webadmin get versions" properly showing the list of backups.

After installing KB4552940 as part of the Extended Security Update for Windows Server 2008 R2 the wbengine.exe in the system32 folder is updated. What happens due to this is that the Microsoft-Windows-Backup service is unable to log Event 4 "The backup operation has finished successfully" & Event 14 "The backup operation has completed" to the Eventlog. After creating an Event Trace Session what you will see for these events is "The description for Event ID 4 from source Microsoft-Windows-Backup cannot be found." below that also saying "the message resource is present but the message is not found in the string/message table".

The BlbEvents.dll & BlbEvents.dll.mui files the EventMessageFile uses are not updated as part of this update so it seems the newer version of wbengine.exe is unable to find the strings it's looking for within those files. Replacing the wbengine.exe dated 4/16/2020 that came with this update, with an older version of the wbengine.exe file dated 3/2/2011 restored this functionality and allowed the server to report backup events as expected.

Side note, start events and failure events are still logged so it seems it's only some event descriptions it's unable to find. This is reproducible by freshly installing Server 2008 R2, and running all windows updates on a machine eligible for Extended Security Updates.

We're having issues with IIS 10.0.17763.1, if you want to use a domain service account as the identity on a web site then that web site as stated here that needs to be granted "Impersonate a client after authentication" in the user rights assignment in the local security policy ...

https://techcommunity.microsoft.com/t5/iis-support-blog/500-internal-server-error-when-accessing-the-root-folder/ba-p/1480940

...failing to do so results in 500 errors on static content...

The main issue with this is what does setting a custom account for the identity of the Application Pool have to do with Impersonation? At best it's misleading. We not using impersonation, we're simply changing the Application Pool Identity. This seems more like a bug than by design.

When trying to cook up an Image for our cloud deployments on Windows Server Core 20H2 with the Server Core App Compat FOD
we are starting with a Nov 2020 Patched windows Core SAC image, and then we are trying to add the App Compat FOD.

But after installing the App Compat FOD, the Get-updates want us to also reinstall the Nov 2020 15 GB patch

It seems that the installation of the App Compat FOD , installs old libraries , and then even if that OS is patched, now a new OS patch has to be installed.

this is a problem . because we are building new immutable images using Marketplace AMIs on AWS, and the building of the new AMI should now require that we use an OS patch , as we expect the OS patch to be in the base AMI.

This bug is in the Android RD Client and RD Client 8. The problem is exposed by running either client on Chrome OS with multiple monitors. When running under this configuration, the display resolution does not ever match the resolution of the external display, even when the RD Client window is moved to the external display and even when attempting to use custom resolutions. In fact, the mouse pointer is off because the mouse pointer assumes the larger external display resolution for its x,y location and the actual image from the remote computer is much smaller, shoved in to the upper left corner.

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.