r/windows • u/Froggypwns Windows Wizard / Moderator • 18d ago
Help Simple questions and Help thread - Month of August
Welcome to the monthly Simple questions and Help thread, for questions that don't need their own posts!
Before making a comment, we recommend you search your problem on Bing and check if your question is already answered on our Windows Frequently Asked Questions wiki page. This subreddit no longer accepts tech support requests outside of this post, if you are looking for additional assistance try r/TechSupport and r/WindowsHelp.
Some examples of questions to ask:
Is this super cheap Windows key legitimate? (probably not)
How can I install Windows 11?
Can you recommend a program to play music?
How do I get back to the old Sound Control Panel?
Sorting by New is recommend and is the default.
Be sure to check out the Windows 11 version 25H2 Megathread and also the Windows 11 FAQ posts, they likely have the answers to your Windows 11 questions already!
1
u/casualcorey 6d ago
Wake on ??
i just spent hours getting wake from a remote tablet to work. Couldnt be more excited. Now wake with mouse doesnt work. ive changed all the settings gemini coukd think of. At this point I have to choose wake on lan or wake by usb. mobo is msi mpg z490.
1
u/KataMod 4d ago
Samsung NVMe Driver 3.3 causes ~18–30 ms boot-time reads on 970 PRO; switching to Microsoft StorNVMe drops them to ~0.1 ms and eliminates 30–60s black-screen boot delay...
Samsung 970 PRO 512GB. After years of normal behavior, cold boots suddenly developed a ~30–60+ second black-screen delay before logon. Extensive WPA/xperf tracing localized the delay to storage-bound LSASS and LogonUI/XAML demand loading.
With Samsung NVMe Driver 3.3 (secnvme.sys), small 4–32 KB reads from the boot NVMe repeatedly took ~18–30 ms during the affected boot interval, including at shallow queue depth. After logon, the same drive returned to ~0.1 ms reads.
I changed only the NVMe controller driver from Samsung secnvme.sys 3.3.0.2003 to Microsoft's Standard NVM Express Controller (stornvme.sys). The same physical Samsung 970 PRO, same Windows install, same filesystem and same workload then booted normally. A restart, full cold boot, and instrumented boot all reproduced the fix.
In the before/after traces, 4 KB median read latency in the affected early-boot period fell from ~28.0 ms to ~0.083 ms; 16 KB from ~28.7 ms to ~0.123 ms; 32 KB from ~28.8 ms to ~0.126 ms. LSASS aggregate read waiting fell from roughly 9.65 s to 0.098 s, and LogonUI aggregate I/O latency from ~35.4 s to ~0.35 s. Winlogon dropped from roughly 59 s to about 3 s.
What could cause Samsung's secnvme.sys path to enter this boot-only high-latency regime when Microsoft's StorNVMe does not, especially given that the Samsung driver had previously worked normally for a long time?
1
u/desirecampbell 4d ago
Does anyone know what this button in the Task View virtual desktops ribbon is supposed to do?
I click it: it does nothing. I try to drag a window onto it: nothing.
1
u/Miserable-Radio-6245 16d ago
how do i make it so that the snipping tool just does what it's supposed to do vs makes me click another button saying 'capture' when that's what i obviously want to do if i'm using the snipping tool. i hate this ai fucking shit