I want to use Graphics diagnostics tools in c# application. In VS 2015 Community, Debug -> Perfomace profiler. Then I click to GPU Usage and start application. "The Graphics Tools opnational feature needs to be downloaded and installed". Ok. Error in installer: "The Graphics Tools faild to install. The DISM installer reported error 87". And link to msdn how to solve a problem. I do all what I see in instruction, but there is a trouble at step 3. There is no components for installing. Why?
System: windows 10 corporate,
Version 1607,
Build 14393.447
Thank you!
I get the same issue because my machine is in a domain with some policy limits. After I remove the WUServer value from the registry key of HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, the Graphics Tools will be listed in Add New Features list.
Please check whether your machine is in a domain with some policy limits. If there has a WUServer value set, it means your machine is managed by the domain policy, please contact your company IT supporters to remove this limit.
go regedit → HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU and change UseWUServer to 0, after restart you will able to install Graphics Tools from Add or Remove Programs → Mange optional features → Add a feature. After successful installation change UseWUServer back to 1 and reboot your machine.
To install graphics tools needs enable and start > Firewall and Updates at Windows Services. After all stop and disable this services.
Here guide how install >> https://learn.microsoft.com/en-us/windows/uwp/gaming/use-the-directx-runtime-and-visual-studio-graphics-diagnostic-features
Or video at youtube >> https://www.youtube.com/results?search_query=graphic+tools+windows
Related
If not mistaken,the error occured after I misclick a notification of a antivirus software that request for a permission.My computer is using Windows 10.May I know how to solve this problem?
Older answers on this software installation:
Node.js - Cannot Install it is showing an error because of .msi
Node.js install fails on Windows 10 1803
Blocking: This sort of problem can definitely be caused by an anti-virus software blocking access to the MSI in question. Disable the anti-virus temporarily and try again. If unable to do so, perhaps try to install on a virtual machine? (for testing or real use).
Windows Installer: Just to get it out of the way: I see some recommendations to re-register the Windows Installer components, but I prefer to eliminate other causes first (a broken Windows Installer usually indicates more serious system-wide problems - such as malware infection, or full disk or something else very fundamental).
Virustotal.com: Before temporarily disabling your anti-virus (the procedure for this is obviously different for each vendor), you should verify the actual binary or MSI using the virus checker interactively and also upload the file to https://www.virustotal.com/ to make sure the MSI isn't actually infected - if it is your anti-virus is doing its job.
Re-Download: It is also a good idea to re-download the MSI from the vendor site in case it has gotten corrupted during download. This happens very frequently. I have seen days wasted with corrupted installation media the unexpected cause. Virus test this new download too using https://www.virustotal.com/ (you want to check both old and new binary for malware - the file available for download can be infected).
Other Causes: There are a number of other causes that are common for failing installers. I have several older answers on this, but maybe this is the easier one to browse: Common causes of failed installations (setup.exe or mysetup.msi fail to install). Here is a quick extract (please do visit the link):
The most common issues seem to be: security software interference, malware infected machine, corrupted download, missing runtimes, out of disk space, blocking mechanisms on the machine from corporate policies, etc...
Other Links:
WiX, deployment and setup links
I cannot reinstall node.js on windows 10
I think your problem is not from the node.js but from the Windows installer itself.
I solved mine by following the instruction here (from the Microsoft forum).
Method 1:
Perform System File Check (SFC), and then check if this fixes the issue.
Follow the steps:
a. Press “Windows Key + Q” to open Charms Bar.
b. Type “cmd” without quotes in the search box.
c. On the left pane, right-click on the “cmd” option and select “Run as Administrator”.
d. Type ‘sfc /scannow’ without quotes and hit enter.
Method 2:
I would also suggest you to run the System update readiness command. It detects incorrect manifests, cabinets or registry data, it may replace the incorrect data with corrected version available. Follow the steps.
4. Press Windows key + X.
5. Click command prompt (run as administrator).
6. In the Administrator: Command Prompt window, type the following commands. Press Enter key after each command:
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
In my case, the first method solved the problem.
While installing my msi i get the follwing error
Error 1935. An error occurred during the installation of assembly component {98CB24AD-52FB-DB5F-A01F-C8B3B9A1E18E}. HRESULT: 0x800736B3. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.VC80.CRT,type="win32",version="8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"
I do carry Microsoft_VC80_CRT_x86.msm in my MSI. But the problem is that i do not see this issue in all machines. This is faced only on a 2012 Windows Virtual machine.
Can anyone please tell me why this error would normally come?
I think you have a corrupted windows O/S. Otherwise it is correct to test on VM's configured with a variety of virgin operating systems that you want to support. Additionally I highly advise to never use this merge module. Instead using a bootstrapper/chainer (WiX Burn, InstallShield Setup Prereqs or Suite Installation ) to install the stand alone versions of the redist from Microsoft. This helps draw a line in the sand between a Microsoft problem and a problem with your installer. It also makes upgrade servicing easier.
I got the same error message on windows 7 (32bit).
This was caused by a failure in windows update for my case.
After that, I cannot install any other program on the computer. I searched from internet and found suggestions made by Microsoft engineers: repair the system from Original Installation disc with "update to latest" choice unchecked.
However, I found another simple solution which also works for my case.
1． Click START>> and type “regedit” to run register editor;
2． Find the following directory in register: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control;
3． search by F3 for the key RegistrySizeLimit and double click the DWORD;
4． Change the key value into ffffffff(Hex) or decimal 4294967295, then click OK;
5． restart the computer;
6． run cmd.exe with Administrator's privilege, and type SFC /SCANNOW followed by Enter in command line; this scanning may take several minutes until the status is 100% and finishes;
Then the problem can be fixed!!
I got this error in my Win7x64 VM after I installed .NET Framework 4.5 required by my MSI. I had a fresh OS install with no Windows updates, plus VS2005 SP1. I ran this Microsoft FixIt: http://support.microsoft.com/kb/976982/en-us, but it did not help until I restarted the VM. Once I restarted the VM, the error disappeared. I think all I needed was a restart, but I provide the above details in case it was the FixIt that actually fixed it.
On a windows 2016 server, I solved the problem by resetting DCOM security to default
launch dcomcnfg
then set Default Authentication Level to Connect
and Default Impersonation Level to Identify
Whenever I try to get my developer's license in Windows 8 Professional with WMC for Visual Studio Ultimate with Blend, I get this error:
We couldn't get your developer license for Windows 8. (Error 0xC03F1014)
How do I fix this error to get my developer's license?
If your copy of Windows 8 is cracked or activated illegitimately then you'll get this error.
If for whatever reason you don't want to / can't get a legitimate copy, then deactivating the crack to go back to the trial period, acquiring the license then re-activating it should fix this issue.
Try to follow these steps:
Create a temporary user account in windows 8
Install a fresh copy of VS 2012
Now try again. It should work now, then log out again and go back to your normal account. Now develop apps and deploy it. Hopefully it works for you.
You need not re-install the OS or the Visual Studio
Start the Task Scheduler service. This is usually disabled in enterprises/large organizations via Group Policy.
This situation happened to me after installing Windows 8 Pro Upgrade as a CLEAN installation. The problem was that the valid License Key failed to activate because a previous version of windows was not upgraded. Because it wasn't activated properly, the Developer License would also not register.
The following steps enabled me to activate the clean install:
Run the registry editor (regedit)
Find the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE
Change the value for 'MediaBootInstall' from 1 to 0
Open an elevated command prompt (run as admin)
Run the following command: slmgr -rearm
Reboot
Open an elevated command prompt (run as admin)
Run the following command: slui 3
Activate your valid Window 8 Pro Upgrade License Key
After my Windows 8 was properly activated, the Developer License renewed with no problems!
I was facing same issue. Error was due to Proxy Server. I was using internet by setting proxy server. U should have open internet to get the developer license.
See these type off error occurred to me . The scenario was I was connected to a proxy server and my proxy server was not allowing popup logins .
Check your internet connection and If the problem is not solved, reinstall VS
Run Visual Studio 2012 as administrator. It should prompt you automatically for the license. I had to login to my MSDN account at this time. If it doesn't come up, then go to Project -> Store -> Acquire Developmer License. This is what did it for me.
I had the same issue, with the additional information that there was a problem with the network (even though my network was fine).
For me, the problem was that my own user is a limited/normal user and doesn't have administrator rights. I did get a UAC prompt when I tried to get a license and I elevated the process to use my separate administrator account, but it didn't work.
What did work however was logging out from my normal user, signing in as my administrator account and try to get a developer license that way.
So apparently running under a non-privileged user is not something that VS2013 appreciates in scenarios like this. I'm not sure why there is a difference between elevating a process' rights through UAC and actually logging in as an elevated user.
Make sure you have all Windows Updates installed. If you can't update:
Install KB2913270 (x86/x64) (original info by Ahmad Wahid, thanks :))
Other tips:
Check the system date and time (it must not be ahead on their systems)
Try to disable NlaSvc service (Network Location Awareness)
In VS2010 Beta 2, from the Help Library Manager, after selecting local help, and downloading the VS Documentation, it won't launch.
Here's what I have installed:
Here's what I'm clicking in the Start Menu:
Here's the result:
Ideas?
Thanks,
Adam
I recommend reporting this bug on Microsoft Connect so that the Visual Studio product team can take a look at this.
This seems like a rather specific problem and not a general programming question.
I also had problems with VS 2010 Beta 2 help, or rather with MS Help 3, which is new with 2010 . There is a known issue with the Help Listener Service trying to listen on port 80. MS document a procedure to change this port, and my help was back up after following it. From the the ReadMe_ENG.htm file that is installed with MS Help:
Removal of Help 3.0 will not remove content from user's machine;
they should run HLM to remove content
Product Documentation shortcut will not work after uninstall of Help
3.0
Help Library Manager requires the BITS service to be running if you
want to use the “Check for Updates” or
“Find Content online” features.
Removing content and installing
content locally does not require the
BITS service.
Help Library Manager will hang if you attempt to install offline
content but there is not sufficient
disk space for the BITS service to
download the content
If port 80 is used by another process (not via the http.sys service)
then the Help listener will not be
able to attach and use port 80 and
will fail. The port number can be
changed by adding a string registry
value ListenerPort under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help3
with the value of the port to use (eg.
81). Due to the http.sys ACL settings
it is necessary to run the following
http.sys configuration command from an
admin elevated command line. On
Vista, Win2k8, and Windows 7 run the
following native command: netsh http
add urlacl url=http://127.0.0.1:/help/ sddl=D:(A;;GX;;;WD)
On Windows Xp, and Win2K3 run the
following command:
httpcfg set urlacl /u
http://127.0.0.1:/help/
/a D:(A;;GX;;;WD)
If the command is not found then it
might be necessary to download the
httpcfg.exe from Microsoft as part of
the Windows XP Service Pack 2 support
Tools
(http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en).
Now the Microsoft Help Listener will
run on the selected port number.
ADDENDUM:
I also ended up installing MS Help 3 manually, and using the Help->Manage Help Settings menu command. On the VS 2010 installation 'disk', I ran WCU\Help\HelpSetup.exe, after removing help via Add/Remove programs. Note the folder HelpSetup installs to, and then in VS 2010, open the Help Library Manager (Help->Manage Help Settings), then Find Content on Disk, and then supply the location HelpSetup installed to. Help 3 will take it from there.
In Visual Basic 6, when I attempt to access Project > References, it throws an error:
Error accessing system registry
I am:
Logged in as the local computer administrator
running Windows XP Professional and
I can execute regedt32.exe and access all the registry keys just fine.
VB6 was installed as the local administrator.
Any idea why this happens?
I'm running crystal reports 8.5 and it supposed to already have fixed that issue but apparently I still have the issue with 8.5 installed. I have also made the attempt of reinstalling crystal reports with no luck on the issue.
Depending on the Windows OS you have (I have Windows 7 Enterprise), you might want to try giving administrator rights to the REGTLIB.EXE (located in C:\Windws). Right click on the REGTLIB.EXE file. Select Properties from the pop-up menu. Then select the Compatiblity tab. On the Compatiblity tab, check/select the Run this program as Administrator checkbox. Click OK to save your changes. It might take take care of the problem for you. It worked for me. Good luck.
For me this worked:
goto C:\Program Files\Microsoft Visual Studio\VB98
change the property of VB6.EXE by right click->Compatibility In privilege level section, check the option Run this program as Administrator
If you're running Office 2010 (Beta) Word (apparently) writes a restricted registry key. VB throws the error when scanning the registry. The key I have is:
HKCR\TypeLib\{00020905-0000-0000-C000-000000000046}\8.5
For Regmon - Filter for Process Name -> "vb6.exe" and Result -> ACCESS DENIED. Helps find it very quickly.
Fixed it with PSToosl (PSEXEC) to run registry editor. The command line is,
psexec -i -d -s c:\windows\regedit.exe
psexec needs to be run with elevated-permissions.
Edit by Jim: I'm on a Windows 7 (x64) box. Elevated permissions require the PSTools solution. XP can get away with a little less.
You could try Process Monitor to see which registry keys are accessed.
I got this on a machine that I was using for VB6 development. I had been building a lot of COM DLLs from VB6 (without binary compatibility) and the cruft that had built up in the registry eventually got too much.
Have a look at what size the registry is and what limit you have set. I doubled the registry size and then went looking for a good registry hoover.
Here is a solution from Microsoft. It references the Crystal Reports problem, but the solution just uses regedit32 to walk the HKEY_CLASSES_ROOT\TypeLib and HKEY_CLASSES_ROOT\CLSID registry branches for dimmed keys and correcting the security on those keys. There are also instructions to fix the security if regedit32 is unable to access the key. Article ID: 269383
In Windows 7 go to start menu then right click "Microsoft Visual Basic 6" then select properties and click Compatibility from the dialog box that appears then tick "Run this program as an administrator".
Have you tried this? Basically, it seems that it is a crystal reports issue. Hope that helps.
Perhaps worth a try going to the "User Account Control Settings".
Regards,
When I installed VB6 on Win7-64 (using instructions easily found by a search engine), it worked fine. UAC was off -- i.e. set to "never notify."
After a few weeks I turned UAC on -- i.e. set it to its default. VB6 then couldn't compile because of the "Error accessing the system registry" problem. Unfortunately, turning it off again didn't help. Apparently the damage done by turning it on was irreversible. I can't explain why this should be, but that's my experience.
Giving REGTLIB.EXE administrative privileges while leaving UAC off sounded like a great idea, but that didn't work for me either.
Finally, using Process Monitor and PsTools as described in other posts here worked. However, I had to give Full Control to large parts of my registry to Everyone. This didn't apply just to isolated keys. It seems that the compiler needs to add keys to major nodes, so I had to open up these entire nodes.
Aside from the fact that working through these steps took hours, I'm now much more exposed than I was before I tried to increase security via UAC, However, I need VB6 and don't see another solution short of a new computer.
Lesson: Don't use UAC with VB6. Except if you've arrived here it's too late for that.
It's VB6 installation issue. Try to re-intall VB6 on your system. Otherwise open "visual studio 6.0" with "Run as Administrator". Then open/browse your project .vbp file via - New Project -> Existing tab.
I have fixed the problem. But none of the suggestion above worked. What I did is giving everyone full control over the SYSTEM key in the registry. This creats a security break. I am running 64bit Windows 7 with vb6 serice pack 6B.
I'm running Windows 10 Pro (10.0.16299 Build 16299) 64 bit. I was having this error when trying to compile a VB6 DLL.
I saw several answers in this post about running in compatibility mode as administrator. I thought I would first try just running in compatibility mode for Windows XP (sp2). I was able to compile my DLL after checking that box. I didn't need to run as administrator.