Windows 10

[Equisilus]

I’ve had my first real Windows 10 update issue in as long as I can remember. None of the September, October, nor November cumulative updates would install, all with the same error. I figured each would resolve with the next update but since each has the same issue, I started working on troubleshooting. Because they are required for the 1909 update, that won’t install either, of course.

The error code is 0x800f081f for the cumulative updates (and 0x8024200d for 1909, but that’s expected) and everything points to .NET framework 3.5 as the culprit. I’ve run sfc, dism (these corrected some issues), removed .net frameworks and then added them back in (even used an iso and pointed to the .net framework package on the iso). I’ve disconnected USB drives (this is apparently a possible reason for failure?). I’ve run the troubleshooters (no problems found, nothing suggested works). I’ve tried manually downloading the updates to install (all fail). I have the latest servicing stack updates and all other updates have been installing fine. All the .NET Framework updates are successful right up to and including the latest, installed on 11Nov19.

I’m continuing to plug away at it, but it’s a weird one for me. There’s usually something that works, but this one has me stumped so far.

[Calelari]

That the framework updates ok makes this a longshot, but have you tried the .NET Framework Repair Tool?

ETA: As long as I’m tilting at windmills, the Windows Update FixIt might be worth a try too.

[Equisilus]

No, haven’t tried that. I will do so right after my latest fix attempt, and report back. Thanks!

[Edit] It re-registered the Windows Installer but that didn’t do anything to fix the issue, unfortunately.

[Edit 2] Also ran the Reset-WindowsUpdate script to axe out any potential corruption in the files but it didn’t have an effect either. I’m thinking it’s not a .NET thing at all, maybe a permissions issue.

[Balasarius]

Thanks, I’ll give that a shot. It’s really weird. I have my PowerShell buffer set to 3000 lines, and scrolling up the first spike is 1/3 of the way up… which means the top of the buffer is ~2000 lines without a single spike. Of course I’m playing XCOM2 right now and don’t care about my ping at all. And other times, like when I’m playing Conan Exiles, there is a spike 2-5% of the time.

Huh. So my pings have been really good all day. 1-4ms, with something around a .1% instance of a double-digit ping.

Then my wife came home and it went back to this -

Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=35ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=26ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=57ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=42ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=26ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=64ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=49ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=37ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=53ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=39ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Then she went back OUT and it’s back to being fine. It’s her fucking iPhones. She has a 7 and a 9, I think. I’ll do more testing when she’s back.

Googling this issue the problem seems pretty common, but, the examples are far, far worse than mine. The solution offered is to buy a better router. But I have a nice router, so that aint it.

Below is what it looks like when she’s gone. And this is after I setup a mesh, and I’m connecting to the mesh router, so that’s gotta add ~1ms.

Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

[Ginger_Yellow]

Oh well, divorce it is then.

[Becoming]

Is it automatically synching shit from her phone every time it connects to wifi? I had a friend who had the same problem with his wife’s phone just eating all the bandwidth like clockwork.

[inactive_user]

Look, her data isn’t going to mine itself.

[Balasarius]

Is it automatically synching shit from her phone every time it connects to wifi? I had a friend who had the same problem with his wife’s phone just eating all the bandwidth like clockwork.

Yeah, it’s gotta be doing something like that. But more, it’s gotta be doing something wrong. I have tons of bandwidth.

[Becoming]

In theory sure, but unless you have a decent qos going on the router that can easily cause you to experience giant latency spikes if it is treating all traffic equally.

Trivial and not a huge deal for regular use, but anything time sensitive like online gaming it will be noticeable (especially faster things like an fps). Most games have netcode sensitive to latency. It obviously varies, but it’s a very real thing.

[Equisilus]

Just to bypass all the additional troubleshooting, I downloaded the MCT and did an in-place upgrade to 1909. Hoping that takes care of the issue for now on, but won’t know until next updates arrive. The upgrade went flawlessly.

[YakAttack]

Windows Defender or whatever keeps trying to quarantine Process Hacker, a Task Manager replacement. Dunno why.

[Profanicus]

I think it gets flagged because malware can use it to disable anti virus:
https://community.sophos.com/kb/en-us/127467

[YakAttack]

I will have to look for a replacement. The tool is certainly handy in many ways, but the main things I need from it are the animated system tray icons.

[Profanicus]

Or you can use it, and configure Defender to ignore its folder

[instant0]

Or you can use Process Explorer from SysInternals to achieve the same results as process hacker (and possibly more?) - From the looks of things of what PH was offering, anyway.

Process Explorer - Windows Sysinternals

Not sure about Animations.

[rei]

I just reformatted a drive and it doesn’t show up as a destination for Windows 10 games/apps install (drive is accessible and has a letter in file explorer) – does anyone know how to fix this? I think @BrianRubin had this problem.

[BrianRubin]

I’ve not fixed it. It’s intermittent too. Sometimes the games work, sometimes they don’t. Can’t figure out yet why but I’m leaning toward anti-virus or anti-malware program, even though I’ve whitelisted the directories.

[rei]

Piece of shit Windows 10…

[BrianRubin]

Piece of shit Windows 10…

It’s so weird, besides this one thing I’m really happy with it. Compatibility with older games seems even better than Windows 7.

[Calelari]

Is it listed as the save location? The “design” of Windows Store-style apps is they all install to the same package location, but you can tweak it a bit.

Settings -> System -> Storage -> “Save locations” or “Change where new content is saved”

Or, to move individual store apps

Settings -> Apps -> click on the app -> Move