Display problem with legacy graphics drivers after Win10 1704 upgrade

June 12, 2017

There are several prerequisits necessary for future Win10 upgrades, therefore Microsoft forces some driver to be installed to continue Win10 support on that hardware and removes legacy software accordingly.

But this is not without issue on legacy hardware and driver.

One example are the black spaces around the display on monitors connected via HDMI, like Flat TV.

Here are solutions described

https://community.amd.com/message/2799248

http://www.avsforum.com/forum/26-home-theater-computers/1251639-how-i-fixed-overscan-underscan-issues-ati-card-without-catalyst-control-center.html

 


Critical issue between Trend Micro Agent and Windows Defender

June 5, 2017

Since Microsoft Updates from May 2017, there are responsive and performance issues with computer with Trend Micro agents installed.

Logon screen takes minutes, same with logon process and any early apps clicked. Takes up to 15 minutes until TM agent and Windows Defender have taken out their battle.

Today TM published a critical patch which fixes the compatibility for Windows 10 Creator Update version and current TM agents in regards of Windows Defender.

But this new patch now just disables Windows Defender, and again, even you want to activate ‘Limited Periodic Scanning’ (LPS), the feature to use additional Windows Defender protection along with third party antivirus solution, it will be disabled. Not a professional recommendation instead to fix this issue and make the antivirus agents compatible with the LPS feature of Windows Defender.

 


Patch older Windows to be save against WannaCrypt attacks now

May 13, 2017

More here

https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-attacks/


SHA-1 countdown

December 1, 2016

Take a look into this blog post about the future handling of SHA-1 issued certificates

https://blogs.windows.com/msedgedev/2016/11/18/countdown-to-sha-1-deprecation/?WT.mc_id=AID522292_EML_4705309#y0ufLBzkV2eCFvty.97

 


Windows 10 build 1607 Limited Periodic Scanning with TrendMicro WFBS 9 deployed

September 21, 2016

You need to install the newest Patch 1 from Sept 20 to get Limited Periodic Scanning with Defender enabled while TrendMicro Antivirus installed. Without this recent Patch 1 from TrendMicro, you will discover that the enalbed LPS will be deactivated after reboot again.

 


How to change the priority of wireless networks under Windows 10

July 19, 2016

This description here works for Win10 too.

http://www.howtogeek.com/131640/how-to-change-the-priority-of-wireless-networks-in-windows-8/


Windows 8.x and 10 VRAM allocation bug

July 2, 2016

Until now Microsoft hasn’t fixed this bug which came since Windows 8. And it is still bothering on latest Windows 10 version.

Under Windows 7 all DirectX9 games could benefit from an VRAM allocation which could address and allocate VRAM above 4GB if it was available. Since Win8/10 users are suffering from this, as this is not possible anymore and has not been fixed until now.

Here are some resources which makes clear that this as already been addressed to Microsoft a long time and is also a major discusson point on the community already. But nothing happend so far.

ENB – Boris Vorontsov highlights VRAM bug on Win8 and 10

Microsoft Community discuss VRAM bug in Win8 and 10

VRAM bug in Win8 and 10 has already filed as a bug at Microsoft


Wireless Clients fail to associate with SonicPoint

November 27, 2014

During a troubleshooting session a few months ago, we discovered on a SonicWall NSA-250M hotfix, that after this hotfix applied, several wireless devices couldn’t associate anymore. Mainly notebooks, but smartphones and wireless HP printer could associate.

During the above mentioned troubleshooting we decided to stay with the last firmware, as the SonicWall support could not discover what was causing this problem many wireless clients couldn’t associate anymore.

Now they released SonicOS Enhanced 5.9.0.7-17o and exactly this issue is occuring. We rollback to SonicOS Enhanced 5.9.0.6-3o (or any later does the same) and the issue is gone.

Will see what SonicWall will discover when they will face loads of tickets during the next months when people with SonicPoints attached to their SonicWall environment will update to this new released firmware.

[Update]

Now when SonicOS Enhanced 5.9.1.0-220 was released we started a new firmware upgrade activity, making sure, all wireless devices have the newest wireless adapter driver installed.

When the new firmware is updating the SonicPoints, again all wireless devices can’t associate and so get no IP address. Same as on the past sessions regarding this issue.

So we rolled back to 5.9.0.6-30 again, but even after the ‘old’ firmware has also been rolled back on the AP, the clients couldn’t connect. The reason was, because the device came back with all SonicPoint configuration and profiles reset. So we had to reboot with backup settings. After this all wireless clients could connect again.

Could be, that wireless Dell clients or adapter working fine with the new firmware, but we will not support such politics.

If you don’t want to run into such a situation to be forced to replace a large number of wireless devices because of future firmware updates, you better look for more serious and reliable solution vendors.


Remote Desktop Services – Upgrade and Migration Guidelines for Windows Server 2012 R2

January 31, 2014

Microsoft Remote Desktop Virtualisation Team has published a detailed guideline and walkthrough to migrate Remote Desktop Services from Windows Server 2008 R2 to Winows Server 2012 R2 and hints how to migrate or update Remote Desktop Session and Virtualization Hosts as well Remote Desktop Web Access and Connection Broker roles.

You find details here .

 


Problem with new iTunes 11.4.1 on Windows 7 64-bit Clients

January 28, 2014

It seems to be a known issue for the last update for iTunes. Your update will fail and iTunes may not work properly after this.

So better wait for an update from Apple which may solve this.

One option may be a removal of this component as described in the following article

http://support.apple.com/kb/HT1923