windows 10 v 2004

[Deleted member 24505]

Well, i played around with driver signing and couldn't get 2004 to work with my official xbox360 wireless dongle. However, I got a Chinese play while you charge bootleg cable and that seems to have no problem working when my controller is plugged in...

Why you gotta be so obtuse Microsoft.... Why. I don't want to buy into your Xbox One controller garbage.

I'm using a xbox one pad on BT, works fine, or with the cable too

 

[GeForce Junky]

I had the same problem with v2004 and 360 controllers. This fix worked:

2004 Windows Update - How to install drivers for Xbox 360 chinese wireless receiver (Code 28)

 

[FreedomEclipse]

I had the same problem with v2004 and 360 controllers. This fix worked:

2004 Windows Update - How to install drivers for Xbox 360 chinese wireless receiver (Code 28)

Problem solved!

 

[AlwaysHope]

And your point is oh you'd rather stick with an outdated driver and not fix your problem optional (beta) or WHQL are practically the same thing they're both signed drivers

The point is very clear. Only concerned with WHQL driver as recommended by AMD for my specific card under win 10 (to repeat myself again)
But you know more than AMD ?

 

[trparky]

WHQL

You do know that WHQL is nothing more than some fancy ass term that's thrown about that means absolute jackshit now, right? I mean, it used to mean something back when Microsoft had an actual Quality Assurance team but since Microsoft fired them all and it's all nothing but Insider Preview stuff now, WHQL means less than jackshit.

Go ahead, load the latest version. Seriously already. Stop giving yourself a fucking headache and listen to people who actually know what the hell we're talking about instead of listening to such marketing buzzwords (WHQL) that don't at all mean what they used to mean.

 

[Octopuss]

It probably still means more than opinion of some random people on the internet. Just my $0,02.

 

[trparky]

It probably still means more than opinion of some random people on the internet. Just my $0,02.

Yeah well, back in the day it used to mean something. Today? Not so much.

These days, as long as the driver is digitally signed who gives a shit? It'll work.

 

[xtreemchaos]

for the first time with a new windows upgrade i havnt had a problem with anything, i just let the thing upgrade "when it was first released" and forgot about it untill seeing this thread, im touching wood while writing this dont want to temp fate i do realise that touching wood in some parts of the world can mean something else but here in the UK it means to stop bad juju.

 

[erpguy53]

from

Resolved issues in Windows 10, version 2004 and Windows Server, version 2004

Resolved issues in Windows 10, version 2004 and Windows Server 2004

docs.microsoft.com

Certain WWAN LTE modems might not be able to connect after waking from sleep

After waking from sleep or hibernation, certain WWAN LTE modems might show no internet in the Network Connectivity Status Indicator (NCSI) in the notification area and might be unable to connect to the internet.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected WWAN LTE modems drivers installed from being offered Windows 10, version 2004 until the issue has been resolved. If your organization is using Update Compliance, the safeguard ID is 28428232.

Workaround: To mitigate this issue if you are already on Windows 10, version 2004, you can enable then disable Airplane mode. To do this, you can select the Start button, type airplane mode and select it. In the settings dialog, toggle Airplane mode on then off again. You should now be able to connect as expected.

Affected platforms:

• Client: Windows 10, version 2004

Resolution: This issue was resolved in KB4577063. The safeguard hold is estimated to be removed in mid-October.

another 2004 upgrade block expected to be removed sometime in the middle of October (almost when v20H2 is ready to be released to the public)

FYI - the KB4577063 update for v2004 was released THU Oct. 1st - MS listed a ton of fixes for this update

 

[FreedomEclipse]

Ive been getting a lot of "Failed with 0x57 retrieving AppModelRuntime status for package Windows " crashes too. It normally happens when im playing guild wars though. I can play anything for hours any day of the week, all day. every day but as soon as i got guildwars up the game just randomly crashes and i gotta ctrl+alt+del to either force a sign out or a restart to be able to get back to the desktop.

I dont think its an issue with 2004 per se~ It started happening with me in 1909 and thats why i updated hoping 2004 would fix it but the bug is still there.

Been getting a load of these perfnet issues as well

Neither of these i know how to fix.. Ive crushed a lot of other bugs but theres a few left like these two and some queencreek issues.

 

[xrobwx71]

I'm up to 15 computers 3 of which are Insiders, various configs and have zero issues.

Most at work, a few at home.

Hi,
MBAM pro is better than windows pretender so no just stay on 1909/... until mbam stops tagging 2004 as malware just like all other win-10 versions to date lol

I'm not trying to be argumentative but this is absolutely not true. Windows Security/Defender is by far a superior AV for Windows 10. This was not true 10 years ago, but today, it scores as high as any on multiple 3rd party test sites. It has the further advantage of being fully integrated into the OS.

It's not about being right or wrong here or who's smarter. That game doesn't interest me in the least. I simply dislike misinformation.

Try not to get pissed and simply check out my claim. I like to get along with everyone.

All that being said, no AV is perfect, especially if the user doesn't practice safe surfing.

 

[Rock N Roll Rebel]

I use to have a problem with Malwarebytes crashing my system or locking it up but ever since they updated Malwarebytes I haven't had a problem in a very long time. let's hope the next windows upgrade does not mess anything up

 

[Rock N Roll Rebel]

Hi, all I was looking around on youtube and seen a video on windows October update ver. 20h2 has anybody tried it? I googled it and it's still in the insider program. i tried it a long time ago and had problems with it. have they made it better now?

ok I backed up my system then I installed it seems to be working ok I poked around everything is good the install was real short and fast.

 

[Rock N Roll Rebel]

windows 20h2 seems to be working well still. I wonder what are they going to name it when it is released in the mainstream?

 

[erpguy53]

windows 20h2 seems to be working well still. I wonder what are they going to name it when it is released in the mainstream?

October 2020 Update - MS already named 20H2 in late September

Preparing the Windows 10 October 2020 Update Ready for Release

Hello Windows Insiders! We are continuing to prepare the Windows 10 October 2020 Update (version 20H2) to be ready for release. Today, we are releasing

blogs.windows.com

 

[rtwjunkie]

you can install Malwarebytes just turn off all of the real-time protection use it just for scans. I use it that way

Hi,
MBAM pro is better than windows pretender so no just stay on 1909/... until mbam stops tagging 2004 as malware just like all other win-10 versions to date lol

I’ve got three systems on W10 2004. Three of them have MBAM fulltime. On two it is also working with Defender (both MS and MB worked with each other to make sure they complemented each other) with zero problems and zero upgrade problems for several editions of Windows now. Same thing with the third one working happily alongside Bitdefender.

I'm not trying to be argumentative but this is absolutely not true. Windows Security/Defender is by far a superior AV for Windows 10.

I ‘ve found it to be very adequate. Not as much control as I’d like, but I’ll take it. It absolutely works perfectly with MB fulltime, which is a strong positive factor.

 

[Rock N Roll Rebel]

when I first installed windows v2004 which I installed it when it first came out Malwarebytes gave me problems but they soon fixed it so it works good now even with all the protection on

 

[Kursah]

Same here as @rtwjunkie , I have four endpoints in my home that all use MBAM Premium fully enabled and I enabled Defender scans as well. No issues.

I also have several systems (physical and virtual) that only rely on Microsoft Defender, which has definitely improved a lot in the past several years.

All systems are updated to 2004, I started with my main system on day one of release. I push this update out through my home-lab managed WSUS server for all but one system which I have yet to upgrade from Win 10 Home so it isn't domain joined and I decided to leave it looking at MS public update servers to compare experiences with what I authorize via WSUS.

The last time I had an issue with MBAM, it was fixed quickly with an update and honestly I'd have to check but I want to say that was 2-3 years ago. Everyone's experience will be different, but overall I've had good luck with Windows 10 2004 and Webroot SecureAnywhere, BitDefender, MBAM Premium, MBAM Free, Microsoft Defender both solo and combined with previous solutions, and also disabled and left disabled once a third-party solution was deployed.

I surely can't knock Defender anymore, nor will I. While it isn't as thorough as other solutions, its pretty damn good. Mixing that with good habits, using DNS filtering for your LAN devices (OpenDNS, Quad9, Cloudflare, etc.), and utilizing some additional management, I use pfSense (I built a cheap PC which works great) with pfBlockerNG (for IP and domain filtering)and Snort (IPS for WAN, IDS for LAN) along with OpenDNS for Home that my pfSense and DC's point to for DNS, for example.

What I do has proven to be very effective, but I also am a sysadmin by trade too so I love doing this stuff. Simplifying it for more basic end-users, I believe having two AVAM (Anti-Virus / Anti-Malware) solutions on your systems is a good idea as no one solution is perfect but combining solutions especially with more cores, GB's of RAM and SSD's is perfectly acceptable IMHO. Then setup your router to use secure DNS instead of ISP DNS, I usually start with OpenDNS (208.67.222.222 and 208.67.220.220), then quad9 (9.9.9.9), sometimes I'll add Google as a public less secure just in case the secure options are having issues (8.8.8.8). Set your DHCP on your router to use the router as the DNS server. This is pretty effective, fairly simple to do, with no additional management.

You can take it to the next level pretty easily by going to OpenDNS and create a free home account to do more management of what content and domains you want to block or allow for your WAN IP, some routers can check-in directly with OpenDNS, some can't and you'll need to use a small agent on a PC in your LAN. Just looking at OpenDNS uses their default domain list, having the option to use that AND add your own whitelist/blacklist is quite nice. Filtered DNS makes a difference and is worth the time and effort, which ultimately ends up being very low effort and can show you what DNS requests coming from your home are being blocked...the Home (Free) edition doesn't track by LAN IP, just your public WAN IP. You have to pay if you want more features...but what it offers for free is more than enough to help many homes hunker down and deal with lower DNS poisoning risks along having some free and easy content/access filtering to go alongside your AVAM solution(s). MBAM's domain filter works pretty good as well, alongside these solutions makes it easy to crank things up even further. Webroot is pretty good as well IMHO.

Windows 10 2004 has continued to perform great with these kinds of measures being taken, and I expect future versions to continue that. If we start talking about VPN's and road-warrior DNS bleed issues, that's a slightly different matter, but really unrelated to this. But if you're working remotely and have an SSL-VPN client setup on your Windows 10 system and notice that sometimes your queries for office-side resources by hostname don't work, then it is relevant. I still see that a lot. But again, that's not really related to OS security and AVAM solutions, just worth mentioning.