ASP Classic stop working after Windows Server 2012 for x64-based System KB5073698
I hope this will be useful to others. We have a legacy application implemented using classic ancient ASP after the most recent windows server rollup update the ASP pages stop working, without any error message, the worker thread just crashed. It turned out that the network stack was hardened and the old ASP engine did not expect a failure on network operations. I did a short write up here with the solution https://www.linkedin.com/pulse/classic-asp-bug-took-four-days-solve-ridiculous-root-cause-pedruzzi-adw9e
HLK: is there anyone known errata ID #138836 information?
Windows 2025 Server, the Hardware Security Testability Interface Test fail with Intel 6369p CPU. I submitted HLK package with readme errata ID#91130 reply FAIL, errta id#91130 is not coverd for this test failure, please to apply onboarding your model in errata ID #138836 through CSS team. Thanks.
Connect Windows Server Key to Microsoft Account
So I was looking and searching for any thread on the internet, but couldn't find anything... Well the story is... I have a Windows Server 2019 Datacenter Key. And I probably will switch different server providers and tried experimenting on my own little Server in my basement with an old AMD Athlon 2... so my thought was: "Wait if I use my Windows Server Key one time, it will probably become invalid..." So I would like to know if there is any chance I could use my Windows Server Key without worrying that it will become invalid. I remember that you can attatch your Windows 10 key to your MS Account... but on Windows Server... there is no option for that (probably because it's meant more for Enterprise solutions...) But is there a solution for private developers?
How to downgrade Windows Server 2019 Datacenter Evaluation to Windows Server 2019 Standard
I have a Windows Server 2019 standard license. However, I accidentally installed Windows Server 2019 Datacenter Evaluation, so I want to downgrade back to Windows Server 2019 Standard. Please help me. Thank you.Getting Prompted for Username and Password on Internal Web Site, HTTP Error 401.2 - Unauthorized.
I have an internal web site that uses Windows Authentication. This works perfectly on my Microsoft Windows Server 2022 Datacenter Azure Edition which is my developer server. When I tried to put this site out on our test Microsoft Windows Server 2022 Datacenter Azure Edition, with the exact same setup, I get prompted for my Username and Password. It does not matter what I have tried to enter for Username and Password, nothing is ever accepted and it I hit cancel, I get the dreaded HTTP Error 401.2 - Unauthorized. I don't understand why this would work on 1 server, but not the other server. HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.
Upgrading a Server 2012 R2 to 2025
Hi everyone, sadly I was unable to locate any kind of search feature so I apologize in advance for potentially repeating this question. I have an old VM with Server 2012 R2 with a self contained AD, DNS and a connected OneIdentity Manager. I want to upgrade that system to something modern. Since Server 2025 advertises a migration path from 2012 R2 I thought that would be easy to do, but I can't even find any place to get an ISO to upgrade. Naturally I'd like to verify if I can upgrade before shelling out a couple hundred euros on a license. Any suggestions what to do? Regards, Justus WingertWindows Server 2016/2019 AD LDS installation with a specific configuration set level
With the release of Windows Server 2025, AD LDS configuration sets are required to have a functional level of Windows Server 2016 or greater. Unfortunately, there is no documentation on how to create a configuration set on Server 2016/2019 with a specific level or how to raise the level of an existing set. The only article with relevant information says that manually updating the msDS-Behavior-Version attribute of the Partitions container to 7 will not work. https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/lds-service-startup-fails. If I execute the C:\windows\adam\adaminstall.exe /?:answer command, I see that a parameter named /ConfigurationSetLevel exists and its default value is 7, However, when I create a new AD LDS configuration set via the wizard, it is created at the level of 2 by default. If I specify ConfigurationSetLevel=7 in the /answer: file and pass it to adaminstall.exe, the installation fails without any errors. Notably, any ConfigurationSetLevel from 2 to 5 works fine using this method. It seems that it is impossible to create an AD LDS configuration set on Server 2016/2019 and add a replica from Server 2025 to it. Is this correct?
Windows 2022 Server RDS - TaskBar Laggy/Slow/Freeze frequently
Windows 2022 Remote desktop servers taskbar freezing in RDP users We are finding the task bar in all sessions (including admin/local) suffer from a delay of 30-45 seconds (varies) when trying to click on the taskbar i.e. to change applications or right click for task manager.issues with the task bar/random task bar freezing on Windows Server 2022 RDS Once the taskbar has focus its responsive as usual, but once it loses focus i.e. you click back into your application, when you try to click on the task bar its delayed to respond again. This is happening on both our 2022 RDS servers - clean boot doesn't resolve the issue, they are fully patched to date. Troubleshotting steps: -Restart the “Explorer” process -recreate user profile in RDP -update the latest windows patch -Run sfc/scannow -Disable programs on the Startup tab If you know anyone please give a solution/feedback.Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long.
I am moving a web site from Windows Server 2012 to Windows Server 2022. When I open my web site, I receive the error message: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. When I inspected the headers, they were only 640 characters long. I have cleared my cache and flushed DNS to no avail. This error doesn't happen all the time, just sporadically. How do I fix this so that it doesn't happen.
WinHTTP Proxy Service Stopping on Server 2019
I am having an issue with a few of our Windows server 2019 VMs. Every week weeks one of the boxes would suddenly be unable to send HTTP requests. Upon further investigations into the Event Viewer, we found this entry around the start of the issue. The WinHTTP Web Proxy Auto-Discovery Service service terminated with the following service-specific error: The endpoint mapper database entry could not be created. Has anyone ever had this issue or knows a fix? We need to restart the VM for it to rectify as the WinHTTP Service refuses to start using the services control panel. The services on those box support 24/7 products and we don't have anyone on call to restart the box at a moments notice.
