Replies

I did some follow up and here is what I found. An 1809 remoting into a 2004 computer works just fine. The opposite is true also.

But a 2004 remoting into another 2004 is where the slowdown is.

1 user thanked author for this post.

woody

Tried 2004.19041.488 today on my systems and everything looked good until I tried remote desktop. The display was so slow that it made the remote computer almost unusable. I discovered that MS is now using a Remote Display Adapter driver from 2006 (XP?). My machines have Quarto video cards for my CAD work. A few non CAD systems have Intel video cards. Under 2004, all computers used the 2006 Remote Display Adapter driver.

MS can say remote desktop works, is not fit for anything… but they can say it works!

I restored my computers back to 1809. In remote desktop on 1809 the actual video card driver is used and the display is 90 percent of the speed of a non-remote session, not 30 percent.

I would like to thank Macrium Reflect. Without their software I couldn’t keep a MS domain running for more than a few weeks at a time.

2 users thanked author for this post.

woody, jburk07

My only concern is the Hauppauge Extender on my HTPC’s tv tuners. The extender is used for viewing a TV station via a browser on any computer on the network (or internet if you let it through the firewall) by using the tuner cards in the HTPC. I contacted Hauppauge today and they responded with:

‘With all that has happen we have had to shift our focus on other items. But the engineers still have plans to getting it all switched before Flash is completely disabled’.

And if you have any flash content (.flv), Handbrake is very good at converting it to .mp4.

3 users thanked author for this post.

SueW, Alex5723, Cybertooth

All but one of my machines started a ‘getting ready to install…’, got to 90% and then errored out – perhaps because I have domain group policy to prevent Feature Updates. Didn’t click on anything, the process just started when I went to the ‘Windows Update’ settings page.

I have all of my computer upgraded now by using an ISO. Two only upgraded successfully by NOT seeking updates before the upgrade (both hp workstations black screened on reboot). One HAD to have the update done as part of the upgrade as it had a boot error and rolled back on the first try. So, if one way doesn’t work, try the other.

All is fine except for the Trim and DISM issues. I always run a chkdsk /f on C drive after an upgrade as it will cleanup 1,700 to 2,000 ‘marked as used’ entries.

My laptop suddenly stopped playing any audio. I ran the troubleshooter and it fixed it. KB4497165 & the 5-12 Cumulative Update are the only changes to this machine since the last time it was working. All other computers are fine.

I run a DISM Cleanup Bat file with the following commands:

Dism.exe /online /cleanup-image /restorehealth
SFC /SCANNOW
chkdsk c: /f

Last night I ran DISM and it quit at 84%. This is with the .264 update. So not there yet. Perhaps in a month or so.

 

1 user thanked author for this post.

woody

Since Microsoft seems to have settled into a Major/Minor yearly upgrade cycle, I will do my upgrades in the fall. I’ve done this with the 1809 and 1909 feature updates and things have been working just find for me.

Also, since the DISM is not working on 2004 H1, I can’t see installing 2004H1. DISM is to the operating system what chkdsk is the hard drive; so no sale. Also, I’m surprised that the defrag/trim still resets itself after a reboot.

So a 2009 system update is my plan for now.

 

FYI, windows server 2016 std. added a ‘2020-04 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4550947)’.

1 user thanked author for this post.

woody

Just looked at the 2019 server essentials server and defender stopped on it at 10:32 am.

Worked fine until I tried running a full scan, it died. The Restart button did nothing.

Faulting application name: MsMpEng.exe, version: 4.18.2003.8, time stamp: 0x7be0fdee
Faulting module name: mpengine.dll, version: 1.1.16900.4, time stamp: 0x5e70249a
Exception code: 0xc0000005
Fault offset: 0x00000000001d00cf
Faulting process id: 0x1078
Faulting application start time: 0x01d612cff6343637
Faulting application path: C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2003.8-0\MsMpEng.exe
Faulting module path: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{52FB5464-4DA2-473D-B213-2CC5356BD68D}\mpengine.dll
Report Id: 1fd93ea0-c80e-4db2-9e04-16377d26574d

Now I have 100’s of these errors showing up:

The Windows Defender Antivirus Service service terminated with the following error:
General access denied error.

If at first you don’t succeed, reboot!

 

2 users thanked author for this post.

woody, jburk07

Over the last couple of weeks I sent out these 2 emails to a tech. journalist:

March 24th:

‘Since 1709 has been extended, perhaps 1809 (May 12th) will also be extended to this fall.’

March 30th:

‘Since large numbers of people are not working remotely, I don’t think Microsoft will release an update that could introduce problems.

I bet MS will only release one update this year, probably in September after the virus. It just doesn’t seem like the time to introduce a variable into a working system.

And then there is the bandwidth needed for this update. The internet is running at near capacity now.’

Lets see if common sense will prevail.

1 user thanked author for this post.

woody

Fixed now on my servers.

I use O&O ShutUp10 to eliminate telemetry being sent to Microsoft. Fortunately I made an ‘OEM’ profile before making changes as to what is being sent to Microsoft.

I reverted back to the ‘OEM’ profile and the KB4052623 update was successfully install on both servers after a reboot. Apparently, no telemetry, no av platform updates, at least on the servers.

No problem on my Windows 10.1809 machines.

This explains why my servers (2019) are generating 100’s of installation errors on KB4052623 since yesterday.

1 user thanked author for this post.

woody

‘Fun Facts’ really? It’s an advertisement! This is exactly why I don’t trust Microsoft any more than I need to run my business. They are always trying to see what they can get away with. Most of this seems to becoming from the sales team/manager. Perhaps it’s time to reevaluate that that department.

2 users thanked author for this post.

Cybertooth, Charlie

If I understand what they are doing wouldn’t it be better to call them:

Windows 10: Current Release Monthly Preview Ring
Windows 10: Next Release Preview Ring
Windows 10: Experimental Development Testing Ring

 

1 user thanked author for this post.

woody