Blog's not dead. Yet.
I clicked to automatically disable a problematic add-in in Microsoft Office 2013 (Word, Excel) and I was unable to force Word to enable this plugin at start-up. I had to change a registry key:
For 32-bit: Root\Software\Microsoft\Office\application name\Addins\add-in ID
For 64-bit: Root\Software\Wow6432Node\Microsoft\Office\application name\Addins\add-in ID
Where Root is HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE.
Change load_behavior from 0 to 3. The add-in will than start automatically.
With Windows 10, I have experienced slow updates of desktop icons. When I add a file to desktop, no icon appeared and I had to refresh. But now, all desktop icons are automatically arranged alphanumerically on left side of the screen. When I move an icon and hit refresh, the icon goes back to left. That is an annoying error (no, I do not have auto-arrange-icons turned on). I thought the solution would be quite simple because I was not the only one with this error on the internet. But none of suggested solutions worked for me. I had to use a software called Fences (by Stardock) to keep icons at their places. When I hit refresh, icons go left first, but then they are moved to their right places by Fences.
UPDATE: I mentioned that also folder view settings is not persistent. And I have found a workaround on the net. The issue is caused by ESET (Antivirus or Security). I copy the solution here just in case the original thread will be deleted: Pokračovat ve čtení „Windows 10: automatic desktop icon rearranging and folder view updates errors“
When working with C++ Dll in Windows 10 and Matlab R2015a: Microsoft Windows SDK 7.1 did not work but Microsoft Visual Studio 2013 worked well! Because of .NET 4.0 is not recognized by the SDK, you will have issues to install.
How to install Windows SDK 7.1 (e.g. Windows 7)? Answer by Matworks Matlab:
This is an issue with Microsoft Windows SDK 7.1. It may occur under two scenarios:
1. If you have Microsoft Visual C++ 2010 SP1 (Express or Professional) installed.
2. If you have Microsoft Visual C++ 2010 redistributable packages (x64 or x86) installed.
The details on the issue from Microsoft are below:
http://support.microsoft.com/kb/2717426
http://support.microsoft.com/kb/2519277
To avoid this issue:
1. Uninstall the Microsoft Visual C++ 2010 redistributable packages (both x86 as well as x64) from “Control Panel” > “Programs and Features”. If you have trouble uninstalling them, see related solution 1-NBI41W at the bottom.
2. Install the Windows SDK 7.1. During installation, under the „Installation Options“ menu, UNCHECK the „Visual C++ Compilers“ and „Microsoft Visual C++ 2010“ components.
3. Apply the SDK 7.1 patch from below: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=4422
4. Reinstall the Microsoft Visual C++ 2010 redistributable packages.
x64: http://www.microsoft.com/en-us/download/details.aspx?id=14632
x86: http://www.microsoft.com/en-us/download/details.aspx?id=5555
Samsung Galaxy S II (GT-I9100), představen začátkem roku 2011, začal se systémem Android 2.3 Gingerbread. Samsung aktualizoval Android více než dva roky a tento model oficiálně skončil verzí 4.1.2 Jelly Bean. Systém byl stabilitní pro všechny standardní věci dostačoval. Nebylo však možné k němu připojit nové wearables – hodinky, fitness náramky (např. Xiaomi Mi Band), protože ty obvykle vyžadují nejnižší verzi 4.3 nebo 4.4 a také přítomnost Bluetooth 4.0 BLE (Bluetooth Low Energy). SGS II měl sice jen Bluetooth 3.0, ale čip údajně hardwarově 4.0 BLE zvládá. Je tedy potřeba nainstalovat nový Android, který by tuto funkci zpřístupnil. Pokračovat ve čtení „Android 5.1.1 Lollipop na Samsung Galaxy S II (GT-I9100)“
Tohle není žádný velký objev (převzato ze zahraničních diskuzních fór), jen si sem poznamenávám vyřešení chyby s ovladačem pro Intel Wireless WiFi Link 4965AGN. Žádný vydaný aktuálně vydaný ovladač chybu neřeší. Po probuzení z režimu spánku u Windows 8.1 se Wi-Fi totiž znovu nepřipojí a je potřeba zakázat a znovu povolit adaptér. To je samozřejmě zdlouhavé a režim spánku tak pozbývá svého smyslu. Řešením je neumožnit notebooku vypínat zařízení z důvodu úspory energie a zakázat N režim adaptéru. Oboje se nastaví ve vlastnostech. Mně již tyto dvě úpravy pomohly, někdy je však údajně potřeba udělat ještě něco dalšího.
Yes, another issue about Asus F3jm and Windows 8 64bit. But this can concern many more notebook models – all which use nvidia 179.48 beta driver. This is the only available driver, published in 01/2009. Suddenly, video_tdr_failure blue death of my Windows started to appear after system boot. Windows was able to recover to a previous state but after a while of using it the same error occurred. My idea was that some new update is causing the compatibility crash. So I have forbidden all updates, but the error was still there. So what is my contribution to the issue? :-) After many tries and system recoveries I found out that the problematic update was already downloaded in hidden windows folder (not deleted during recovery) and therefore always installed over and over again even if automatic updates where disabled. So I have deleted all data from update folder and for now I am able to use the system like a charm. Do not forget to renew automatic updates but forbid the specific update which is causing the error. I believe it is KB2976978 from 02/06/2016, which is not important but optional update. Describtion says it tests the system for drivers compatibility in order to enable smooth upgrade to Windows 10. As I already know that Windows 10 cannot be installed, it is useless.
Dlouhou dobu nebylo příliš routerů, které by podporovaly VDSL. A mnoho jich není ani dnes. Zyxel P-870HN-53b VDSL umí, a tak ho možná vlastní nejedna domácnost. Dnes již ale stále více a více PC má Windows 8 a zde nastává problém. Webové rozhraní Zyxel P-870HN-53b se jen velmi neochotně otevírá pod Windows 8. Stránky je potřeba mnohokrát obnovovat, aby se vůbec načetly. Ovládání routeru je tak téměř nefunkční. Zyxel však reagoval, že router již nevyrábí, má novější model a aktualizovat firmware se nechystá. A to ani kvůli takto velké chybě. Takže máme smůlu, musíme na router přistupovat z nějakého zařízení, které neběží pod Windows 8.