Arivia posted:

Update/restart anger.

Flipperwaldt posted:

I didn't dismiss the notifications or tell Defender to make an exception. Just brought Explorer back into the foreground. It'd be like the logon prompt telling me the password is wrong and then logging me on anyway, because that's what I directly instructed it to do.

At the very least it shouldn't be telling me the file is in quarantine when it clearly isn't.

Jeb! Repetition posted:

How do you view a stoplog in Windows 10? Or more to the point how do I find out what caused my system to crash so badly it had to restart

Grump posted:

Just unboxed my new Windows machine and Windows 10 keeps freezing about 15 mins after startup. No idea what could be causing it. I have 16GB of ram, so I don't think it's a memory leak issue. It's just freezing with no indication of what's going wrong....weird.

fishmech posted:

Quarantine doesn't mean you can't go access it. In fact quarantine is explicitly designed so that you can go access it instead of it being outright deleted.

Jeb! Repetition posted:

How do you view a stoplog in Windows 10? Or more to the point how do I find out what caused my system to crash so badly it had to restart

Grump posted:

After some googling, I think there's definitely some compatibility issues with Windows 10 and SSDs.

Flipperwaldt posted:

My previous experience with Defender on Windows 7 and 8 has been that the file automatically got removed from the folder, into quarantine. Then, if you wanted to interact with it, you'd have to go through Defender's interface to move it back out of quarantine. A thing which also would require admin rights. This is also exactly what happens on Windows 10 if the exe file isn't in a zip file.

This whole "you double clicked a thing I consider dangerous, so I'll let you know, but also, keep the file where it is and just run the program in response to that double click anyway as if nothing is wrong" is new to me and I don't know how it can be considered the name quarantine worthy.

mobby_6kl posted:

My tablet has been trying to install the 1709 update several times now and it fails every single time. In the update history it just says "Feature update to Windows 10, version 1709 / Requires restart to finish installing" four times without any error messages. Any ideas what could be the issue?

fishmech posted:

Windows 7 and 8 MSE/Defender for me has always had the same exact behavior you described for a dodgy exe file in a zip that wasn't labeled severe enough to be an instant deletion thing.

Things marked for quarantine are inherently considered to be lesser threats, so they correspondingly get lesser response and the system won't hard-block you the way it attempts to do for more serious "threats".

BangersInMyKnickers posted:

It's probably still an AV conflict. What's your Win10 build number?

e: Might also be a warning that your BIOS doesn't mitigate spectre if MS is getting clever.

Flipperwaldt posted:

So-called severe threat, says so in the quarantine list! Can't verify what Defender on Windows 8 would have done because it doesn't consider the program a threat at all. But I remember it was at one time impossible to have a copy of Nirsoft's WirelessKeyView outside of the zip file it came in, even just the temp copy created when trying to run it from inside the zip. Would be moved to the quarantine instantly. Could not run it at all without making an explicit exception. I'd like to think that's still what would happen with a severe threat. Of course, WKV is now downgraded to a medium threat apparently and you can do with it whatever you like. It takes forcing a scan of the file to even get the suggestion to maybe do something about it, if you like, so there goes that test case.

Also both Defenders are super fine with the program now that I've changed compression settings in the compiler.

fishmech posted:

I'm not following now... You're mad that a fake threat you generated doesn't get picked up and that something that was overzealously blocked in the past is now degraded as a threat but still has Windows tsk at you like it will for certain keygens for old software?

Flipperwaldt posted:

I am disappointed that Defender on Windows 10 doesn't flat out stop me from running something it considers a severe threat as my previous experience on Windows 8 was that it would. As supposedly supported by the WirelessKeyView on Windows 8 anecdote, that I now can't prove or demonstrate anymore. I would like to demonstrate that both Defenders behave differently in case of severe threats, to sort of refute your suggestion that it may be related to how MSE/Defender always reacted to low severity threats, but I'm running out of false positives that I'm willing to try to run on my system for the purposes. It annoyed me that I went through the effort to try and found that WirelessKeyView didn't offer me additional evidence.

I am also surprised Defender on Windows 8 doesn't use the same definitions as Defender on Windows 10.

The threats being fake is incidental to the story. The creation of a program that was detected as a severe threat was completely unintentional. I prefer it not being detected as a threat at all, as it isn't. That doesn't stop me being of the opinion that if Defender really thinks it's a severe threat, that it should take adequate measures.

BangersInMyKnickers posted:

Check if your build number is 16299.192 or if KB4056892 is installed.

fishmech posted:

Dylan16807 posted:

Defender is absolutely not taking adequate measures for a threat labeled 'severe'. Defender is claiming to quarantine the file without putting it into quarantine. Defender is then letting the file be run from its original location.

If you're confused by the mentions of non-severe threats, just ignore that part of the post. It's not the important part. The core complaint is about the handling of a 'severe' threat.

Dylan16807 posted:

Defender is absolutely not taking adequate measures for a threat labeled 'severe'. Defender is claiming to quarantine the file without putting it into quarantine. Defender is then letting the file be run from its original location.

If you're confused by the mentions of non-severe threats, just ignore that part of the post. It's not the important part. The core complaint is about the handling of a 'severe' threat.

skooma512 posted:

Would you happen to know anywhere that details those changes? I switched last month, but I’d like to know what I got for the effort besides the Microsoft store and lock screen wallpaper.

tight aspirations posted:

I had this on my desktop, and solved it by downloading the media creation tool, which then succeeded in updating Windows.

PUBLIC TOILET posted:

Nope and nope. I'm on 16299.19 and that KB is not installed. Tried to manually install and no go.

BangersInMyKnickers posted:

You can manually download the KB off the MS catalog site. Give that a shot https://www.catalog.update.microsoft.com/Home.aspx

BangersInMyKnickers posted:

No, MS is still rolling the KB it's hardware vendors that are withdrawing the BIOS/microcode update because of compatibility issues with some processors.

dissss posted:

The January updates are no longer installing on Haswell or Broadwell systems for me even though they’re approved in WSUS and haven’t been superseded. It’s still installing on Skylake systems.

CubanMissile posted:

Is it normal for my optical drive to only show up in File Explorer if there is a disc inserted?

beuges posted:

In Explorer, select the View ribbon, click on Options, and under the View tab there's an option that's ticked by default called 'Hide empty drives'.

VostokProgram posted:

I added another SSD to my computer and I just realized it's showing up as a removable disk. I believe this also happened the first time I added a hard drive, but I don't remember how I made windows treat it as a local disk. Anyone know how to do that?

quote:

The fix to the 0x80243004 and 80243004 errors for Windows Update is overly simplistic, but definitely worth retaining considering the problems are reported pretty regularly.

Per KB2837515, the cause is that the Automatic Update client requires that the tray icon be managed either by Group Policy, or that it be displayed if not disabled by Group Policy.

And, again, the fix is a simple one:

In the notification area at the far right hand side of the taskbar, click the Show hidden icons button and then click Customize.
In Notification Area Icons, under Icons, scroll down to find Windows Update. Click the drop-down list next to it, click Show icon and notifications and then click OK.


Go to Windows Update and check for updates again. It should now complete as expected.