This description here works for Win10 too.
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.
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 220.127.116.11-17o and exactly this issue is occuring. We rollback to SonicOS Enhanced 18.104.22.168-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.
Now when SonicOS Enhanced 22.214.171.124-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 126.96.36.199-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.
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 .
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
Since Skype versions 6.1x and especially 6.2x and now 6.3x many people facing problems with network connections after starting Skype. Even not be able anymore to logon to Skype, because the network connection is blocked.
When you open the status for your network adapter, you can see that there are not any byte received and send anymore. And after a few seconds you get notice that there is no internet connection anymore.
Not enough, you recognize starting IE or Explorer takes time, if you are anyways be able to open them.
Once you terminate Skype everything returns.
It doesn’t matter if you disable UPnP in Skype or you disable using alternative port 80 or 443 to receive incoming calls.
Sometimes it helps for a while if you let the network wizard resolve problems with the network connection. But be aware that the issue returns when you start Skype next time.
If you find event ID 11609 in your event log referencing to your Skype installation, this is related to what I described.
Here are some links if you like to read more about…
After applying KB2444677 Hotfix, Problem was solved. So it seems it is related with special handle execution on Explorer internals.
Problem turns back until it was solved for a while. Now thinking about finish with Skype, as this seems ongoing issue when reading community forums.
Seems now been fixed with Skype version 188.8.131.52 hopefully
Maybe you remember setting the WLAN / LAN switch on your notebook BIOS, disables your WLAN adapter when you plug in an Ethernet cable to your NIC and enables the WLAN when it is unplugged.
This feature, even if it is correctly configured in the BIOS of your notebook, it will not work on Windows 8.
Sadly you have to manually switch adapters on or off under Windows 8
Starting with IE10 installed, I faced lots of crashes and hangs.
Searching for some troubleshooters I found this helpful
If you want to move VHD files you have to take care on certain permissions on configuration files and directory rights. Otherwise you will not be able to start your VM.
For more details and how to solve this read this articles.