With the Update/RTM to Microsoft Windows 8.1 you are not able to use the Microsoft Unified Access Gateway (UAG) 
features of the Company you work for or your Customer.
At least you are not able to open an SSL connection or start the RDP session to a server.

This has been caused by a false detection of your Windows and Browser Version by UAG itself. Don't ask why 
Mcrosoft dows not release a hotfix to fix this for their customers with ease ...

... no one can understand their train of thoughts.

Many tried to edit their web.conf file but did not get a final, easy working solution :-(


First of all - it's not the easy, one button and everything is fixed solution that I tried to achive. But it's the only 
working one I'm aware of.
Hopefully this workaround is not needed when Microsoft releases a patch/update for UAG in Q4 2013.

You have to go through four steps:

  1. Software prerequisites:
    Receive the UAG client components (WhlClientSetup-all.msi) from your administrative contact 
    (because it won't install from the UAG Portal).
    It is located on the UAG server install directory (default path: C:\Program Files\Microsoft Forefront 
    Unified Access Gateway\von\PortalHompage\)
    Install the "WhlClientSetup-all.msi" with all features enabled.

    If you use a third Party Firewall that will be detected by UAG everything will be fine. If you use the 
    standard Windows Firewall it's possible that it won't detected correctly and access to some features 
    will be denied. You can check if your firewall setup will be detected by clicking the Button "system 

    picture of button

    UAG system information
  2. Start your Internet Explorer and add the domain you try to log on via UAG to the list of sites that are 
    opened in compatibility view.

  3. Restart your Browser and enter the UAG portal address.
    When loaded press F12 (Developer Tools) and set the parameters of the site as followed (or 
    shown in the screenshot below):
    Document Mode: 9
    Useragent String: Internet Explorer 9
    When changed then log on with your personal credentials.
    You will see everything will be available exept SSL.

    click to show screenshot with settings

    UAG settings for use of all features
  4. To use SSL please log off (but dont't close IE) and log on the UAG portal.
    Everything should be fine now - SSL should be available too.

Be aware:
Step 3 and 4 have to be done at every new logon to the UAG Portal page!!! 
The Developer Tools settings are not persistant!!!

Update log:

1.1 - 2013-11-27 - added information about firewallsetup in step 1

1.0 - 2013-11-26 - initial version of article

Mit dem Update von Windows 10 Build 1803 auf das Herbst-Update 1809 hat Intel offenbar einen Bug eingeschleppt, der den Intel Grafiktreiber bei bestimmten Systemen auf den Auslieferungstreiber zurücksetzt.
Scheinbar läuft in Windows ein mal pro Tag ein Task der den aktuell installierten neueren Treiber durch einen alten Treiber zurücksetzt ( vom 24.10.2016).

Betroffene Hardware:

  • Intel Core i7 6500U mit Intel Graphics 520

Betroffene Treiber:

  • Intel HD & Iris Graphics Drivers Version WHQL


Bestimmte Anwendungen, die bestimmte Funktionen des Intel Grafiktreibers einsetzen, funktionieren nicht mehr.

Betroffene Software:

  • DxO Optics Pro 11
  • DxO PhotoLab 1.x

Ich habe heute versucht, das Problem dem Intel Support zu melden.
Dies war nicht möglich, es wurde nur ein automatischer Rückruftermin am 09.10.2018 - 09:45 Uhr vorgeschlagen :-/


FileHistory to an NetworkAttachedStorage (NAS) is your perfect buddy in every day file versioning and easy backup. Everything worked like a charme.
You decided to move to a new storage, reinstalled it but used a new hostname or even only changed the hostname of your NAS system.


Windows FileHistory stopped because the old NAS-Hostname is gone or it contents could not be found.

Solution (valid for Windows 8.x & 10):

Easy ;-)
Open the Windows Explorer on the affected System and logged in User.

Copy text as followed in the adress bar: %LocalAppData%\Microsoft\Windows\FileHistory\Configuration

Microsoft hast made a big step by developing Windows 10 and releasing it today.

I tried to get the update on serveral machines today by using the common way through the GWX updater.
Despite the updater itself got an update it does'nt downloaded the Windows 10 files.

After a short research in www here is a proven failsafe way to force that:

  1. Start Windows Update and receive the latest Updates for your system. Set Windows Update to download and install all updates automaticly.
  2. Start the Windows Explorer, navigate to "C:\Windows\SoftwareDistribution\Download" and delete the content of the folder (not the folder itself!)
  3. Start an commandline (cmd.exe) with administrator rights and execute the command as follows: wuauclt.exe /updatenow
    It will force the redownload of all updates that have to be in the folder mentioned above and it will also force the download of the Windows 10 installation files.
  4. Check if your actions have been successful by starting Windows Update that sould state it is downlaoding Windows 10 files.
Windows 10 downloading

UPDATE 2015-08-03 - fixing further donwload showstoppers

On some machines the Download of the installer will be successful but the installation itself won't - you get some failed to install errors within Windows Update log.
On other machines the Update itself won't show up as available.

Here is another tip to fix that and force the installation of the update:

  1. open the Windows Registry Editor (regedit.exe)
  2. navigate to the folowing string: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade
  3. create a new dword (32bit) and name it: AllowOSUpgrade
  4. open the new entry and set its value to: 1
  5. now juts navigate to Windows Update and search for new updates

Please let me focus your attention to an very well written and perfect summed up post of Michael Niehaus on  MS TechNet:
This is perfect to reduce OS Size on low/midprice devices that come with (very) limited storage space.

2015 11 18win10reducediskfootprint

Heute Stand ich vor dem Problem, dass die von mir verwendete IRC Software "SMUXI" bei Start zwar in der Taskleiste angezeigt wurde, jedoch nicht auf der Arbeitsoberfläche/Desktop. Was ich auch unternommen hab keine sinnvolle Lösung in Sicht.

Auch eine Internetrecherce blieb erfolglos.

logo blue


Acronis Software Partner Logo



Go to top