Forum Widgets
Latest Discussions
Windows 11 Pro, my PC will wake itself back up when sleeping & start itself back up when shut down
This issue started about a year ago. It's annoying, as I am currently living offgrid and need to conserve power to my battery backups easily. I have tried replacing the GPU and the CPU. I have tried adjusting the power saving settings, but I don't know of any settings that are supposed to have this effect anyways aside from waking up for network, and it does this even if starlink is unplugged. Please help me go through troubleshooting steps.
Windows freezes if I try to access speech
I noticed this problem a few days ago after installng Dragon Pro 16 on my desktop computer that when I opened it the computer froze after a few seconds. Both the mouse and the keyboard were unresponsive so I had to switch the computer off and then on again. I had seen some problems with Dragon prior to the freezing so tried uninstalling and reinstalling it, and I also tried a repair, but this made no difference. Thinking this might be a Dragon problem I decided to try Windows Speech Recognition, but part way through the installation process the computer froze. I have also found that if I go into Settings and try to access the Sound options the computer freezes almost immediately as well. Usually within seconds. System File Checker and Check Disk do not find any problems with my computer. It was suggested that it might be a memory problem but removing both memory cards, one at a time, did not solve the problem. At the moment the only thing that I can think of trying is another clean reinstall, after formatting the C drive. As I did that recently I would prefer not to do it again. When I did that reinstall I was surprised to see a few shortcut icons on my desktop to programs which I had not reinstalled, and also the Documents and Pictures folders were mapped to my D:\ and F:\ drives respectivley. I had expected to have to remap these folders myself. If anyone has any suggestions as to how I might solve this problem I will be very grateful. Thanks for reading this.All Windows Troubleshooters will not open
Hi........ HP Laptop 15-dy2048ca (2L7J7UA) Windows 11 Home 25H2 OS Build 26200.8117 Intel® Core™ i5 processor Installed RAM 8.00 Gb First time here in a long time. Anyways, my problem is that none of the Window Troubleshooters will open or run. When I click the "Run" button I get two quick brief flashes from the touchpad cursor, but nothing happens. The original reason I had to use the troubleshooters is that I had trouble getting update KB5086672 -26200.8117 to install. But I was able to get the update to install after I ran an In-place Upgrade. I've tried a lot of suggested solutions, but nothing. as of yet. has brought the troubleshooters back to life. So far., in almost two days I have tried the following suggested solutions: Check Path for Temp Folder Restart Cryptographic Service Run SFC and DISM Scan Run Disk Cleanup Check Group Policy Try to run Troubleshooters in Clean Boot State Enable or Restart Required Services Flush the DNS Cache and Reset the Winsock Catalog Disable Third-Party Security Software and Firewalls Rename the Catroot2 and SoftwareDistribution Folders Modify TEMP and TMP Environment Variables Enable Troubleshooters in Group Policy Editor Performed an In-place Upgrade. Used a System Restore Point. Surely there must be a solution to this that works. Isn't there a download or a program where I can wipe out / delete the whole troublesome troubleshooters section and replace it with a troubleshoot section that works?
DNS-over-TLS on Windows 11: why does the DNS client negotiate TLS 1.2 instead of TLS 1.3?
Hi, We have configured DNS-over-TLS (DoT) on Windows 11 (latest version, 25H2) using: netsh dns add encryption server=<ip> dothost=<hostname> autoupgrade=yes After capturing and analyzing DNS traffic, we noticed that the DNS client always sends a TLS 1.2-only Client Hello, with no supported_versions extension offering TLS 1.3. This causes connection failures with DoT servers that require TLS 1.3. While researching this behavior, we found a Microsoft Q&A discussion mentioning that applications using the legacy SCHANNEL_CRED structure cannot negotiate TLS 1.3, while applications using the newer SCH_CREDENTIALS structure can. Could you confirm whether the Windows DNS client still uses SCHANNEL_CRED for DoT connections? If so, is there a plan to update it to SCH_CREDENTIALS to enable proper TLS 1.3 support? Thank you.
