Today, looking in directory C:\Windows\System32\drivers, I found strangely named file “剐䍏塅ㅐ〰匮卙”. First thought was: it is driver form LG PC suite… I remember, that some files have Korean characters in it. However, looking closer, I found, that file is digitally signed by Sysinternals.
So it can not be a computer virus, because in that case they would need a private key form Microsoft Sysinternals.
I have a couple of programs from Sysinternals installed. So I started to google, but could no find answer easily. Here is a link to relevant discussion. Running logonsessions creates…
It talks, that file C:\Windows\System32\drivers\剐䍏塅ㅐ〰匮卙 is created by LogonSessions utility. So file really comes from Microsoft, so it is not a virus.
Visual Studio 2010 shows the following error: 1>------ Build started: Project: some_project_name_i_am_hiding, Configuration: Debug Win32 ------
1> stdafx.cpp
1>c:\program files (x86)\microsoft visual studio 10.0\vc\include\intrin.h(26): fatal error C1083: Cannot open include file: 'ammintrin.h': No such file or directory
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Error is caused because file intrin.h have reference to ammintrin.h, and after this update there is no such file. Relevant fragment from intrin.h: #if defined(_M_IX86) || defined(_M_X64)
#include <immintrin.h> #include <ammintrin.h>
Installing service pack 1 takes some time while I am writing this blog post… 30 minutes… And Building / compiling after SP1 is successful. So installing Microsoft Visual Studio 2010 Service Pack 1 fixes this issue.
Screenshots from the process below.
VS 2010 about box before installing SP1
VS 2010 installing SP1
VS 2010 installing SP1
WCF RIA Services V1.0 SP1 – installation is taking like forever…
Almost installed VS 2010 SP1
VS 2010 SP1 installation complete
VS 2010 about box after installing SP1… WOW… Licensed to is shown correctly!
Yesterday tried to install ‘Security Update for Microsoft Visual Studio 2010 (KB2455033)’ via Windows update on Windows 7 Ultimate 64-bit but it failed with Code 643. Installation constantly failed with Code 643 – Some updates were not installed.
Currently Google search does not shows anything useful, however Microsoft Connect have listed 4 workarounds. I tried only last one, and it worked.
Posted by AleALEJANDRO on 4/14/2011 at 3:28 AM
It works!
