Recently, one of my users complaining because they he could not activate Visual Studio with his MSDN account. It works fine on another machine, but not his. I tried mine, and I still got the same error - thus it was safe to rule out it is not license / user issues, but more towards computer issue. Error : Microsoft Visual Studio We could not add the account Service returned error. Check InnerException for more details Troubleshooting : Back to basic - let's start from beginning... Trying to sign in will throw this error window. Selecting Close on above window would throw this Security Alert warning.  Selecting View Certificate on above window would give us this.  Let's view Certification Path, and view Root CA certificate by selecting the root certificate in Certification path | View Certificate  So it seems the Root CA (in my case) is issued by Baltimore CyberTrust Root.  Do I have that on that mach

I faced this issue a few months back, where I could not patch one of our servers. Whenever I tried, I will got this : Error :  Windows Update Standalone Installer Installer encountered an error :  0x80070005 Access is denied. Troubleshooting : Troubleshooting 101 - check the service. Turned out, Windows Update service could not be found in the server... Resolution : There are 2 easy ways to resolve this.... Method 01 : 1) Go to a working server. 2) launch REGEDIT. 3) export below Registry key. Registry key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv 4) import to the target server 5) restart the server Method 02 :  1) Apply below Registry Keys to the server : [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv] "PreshutdownTimeout"=dword:036ee800 "DisplayName"="Windows Update" "ErrorControl"=dword:00000001 "ImagePath"=hex(2):25,00,73,0

Another simple post - Where is the location of Outlook Signature ? It is at........ C:\Users\<UserID>\AppData\Roaming\Microsoft\Signatures So there are 3 files :  *.htm - for HTML email format *.rtf - for Rich Text email format *.txt - for plain Text email format all of them can be edited via Microsoft Word. simple as, aye?

I got this error while deploying Windows OS to my environment. It should be straightforward process, but somehow I got stuck with this. Clicking OK will restart the machine, and it still won't resolve the issue. Workaround? run msoobe.exe manually. Issue :  Windows setup could not configure Windows to run on this computer's hardware. Workaround :  Press Shift + F10 , command prompt window will opened  Change the directory to C:\Windows\System32\oobe CMD : cd C:\Windows\System32\oobe  execute msoobe.exe CMD :  msoobe or msoobe.exe  This screen appeared. Proceed with deployment.   Once all done, we'll be back to this screen, restart the machine by using command prompt or just click OK at the message box.

One line script - a quick note for myself. To find the service display name based on service name get-service -Name "<serviceName"> To find the service name based on service display name get-service -DisplayName "<serviceDisplayName">