I've been assigned to download and install the Windows Logo Kit v1.6 to test a driver for Windows 7. What I have done so far is installed the controller and the studio on a clean Windows 2008 R2 64 bit machine. I also have another clean Windows 7 Pro 32 bit as a client. After the installation, the client machine shows in the Studio.
The next step is to install the driver on the client PC. I've tried googling around to find documentation for this part, but I haven't found any.
How do i install the driver on the client PC? Do i just install it the way I always do or is there a special procedures that I need to follow?
At the studio, there so so many tests to run. How do I know which test to select?
I really don't understand what the problem appears to be, especially since DTM.chm is pretty clear on what to do and how and when. The basic steps if you have set up the DTM controller and clients and registered the clients in a "machine pool" are to open the DTM Studio on the DTM controller and then (quoting the online documentation):
Open Driver Test Manager (DTM) Studio.
On the Explorers menu, click Device Console.
Select View By Submission.
From the Submission control, click New Submission. The Create New Submission Wizard appears.
From the Select OS dialog box, click the Windows operating system that is installed on the client, and then click Next.
From the Select Category window, click ...
... and this is were it depends on your driver class etc. So without a refined question no refined answer.
Anyway, skipping a few steps ahead:
Type the path to the INF file and click Load. You can also use the Browse button to find your INF file.
... this is where you are selecting your - hopefully correct and tested - INF file and the rest again depends on what you want to achieve.
If you have an MSDN subscription you also have a number of support incidents "free of charge" per year, which may be a good idea if you get stuck here. However, so far the documentation was reasonable enough to see us through ...
Note again: the whole process depends on your driver class.
Also note: there is a list of errata (Microsoft's terminology). Make sure those are up-to-date and not expired, because if you have a driver class with special needs, some tests will likely fail and you need to select the errata that apply to your driver then to achieve the 100% result required to get it cross-signed. We don't do the full Windows Logo process, though, but the DTM part should be the same anyway.
Related
I am trying to install a legacy VB6 app on a Windows 10 Enterprise PC. The app has an install program and it is installed on many Windows server 2016 machines. This program uses active user documents (dob files) that load in a webbrowser control. The install is successful but when I run the program instead of loading the user document in the webbrowser control i get a dialog box asking me if I want to download or save a 'vbd' file with the same name as the active x dll the user document creates.
My question is if anyone knows if there is a prerequisite to having the vb6 webbrowser control or active x documents work on a Windows 10 machine? I have the dll registered and the registry entries match the Windows 2016 server.
Thanks in advance,
Hank
Here's the relevant (I think) part of the VB6 help for ActiveX Documents:
A few of the more common problems in Internet Component Download and their solutions are listed in this section. These include: [...] Prompt: "Opening file DocumentName.VBD. What would you like to do with this file? Open it or save it to disk?
The proposed solution to this is
This error occurs when the Visual Basic runtime library (MSVBVM60.DLL) is not installed. Generally, this occurs when the safety level in Internet Explorer is set to High. To correct this, you must set the safety level in Internet Explorer to Medium or None.
Note sure when this help entry was written, but with the latest IEs, you add the site in question to the Intranet zone and change the setting there. If that actually resolves the problem, you then should try turning security up again by going into "Customized" and add restrictions again that don't cause it to break again.
Problem: I have an Roland Edirol UA-1000 10-Channel audio interface. It is still as good as what is out there and the last driver update for it was based upon Windows 7. It is hit/miss on Windows 10 compatibility.
What I would like to do is decrypt the driver and update it to work. I'm not sure if that is possible but this interface does much more than anything out there right now (i.e. clocking, optical, midi, coaxial, ADAT, etc.) unless you want to buy 3-4 separate pieces. The driver is just incompatible with Win10.
I have worked as a developer the past 10 years (e.g., VB.net, Java, Javascript, VBScript, SQL, Android) so I would like to try updating the driver for this interface.
Would it be possible... any suggestions outside of "buy something new?"
Check on GearSpace.com. My house in disarray now because we're having some work done so I can't look for my notes. My UA-1000 DOES work with Win 10, there are drivers that work and a procedure to follow and I believe I found the info on GearSpace.com. I just updated my software to REAPER and although I haven't recorded anything yet the meters on my UA-1000 and the input show up in REAPER on my PC so don't go nuts trying to rewrite software.
The only downside to the UA-1000 is the 8 audio in's and outs because if you want to expand to 16 ch's using ADAT and another interface you can't record above 48Khz.
Possible, but difficult. You will need to learn C or C++, a lot about Windows driver APIs, and a lot about reverse engineering. The existing driver may not be much help at all. You won't be able to extract any kind of readable code from it. You would basically be starting from scratch, with black-box observation and/or disassembly of the existing driver as guidelines. It would be difficult work, and the result would be something that would have limited use to other people anyway, thanks to Windows driver signing.
I love my UA-1000 and did get it working on both Windows 10 and 11 using the Windows 7 64-bit drivers from Roland:
https://www.roland.com/global/support/by_product/ua-1000/updates_drivers/
Note: For Windows 11, the install will tell you that "Memory Integrity" security will need to be turned off. There's no way I found to get around it. If you need to turn it back on, uninstall the UA-1000 driver then search for the "Core Isolation" settings and re-enable Memory Integrity. Basically, the old UA-1000 driver isn't built to the latest Windows driver security standards.
Install Steps:
Download Windows Vista 64-bit drivers.
Unzip the archive into a folder.
Connect the UA-1000 to the computer and turn it on.
Right click Start menu and search for the "Device Manager".
The UA-1000 appears in the "Sound, video and game controllers" with a yellow triangle.
Right click on EDIROL UA-1000 and select "Update driver".
Select "Browse my computer for drivers." Point to the folder containing the drivers you unzipped in step #2.
Click "Next" and the drivers will be installed.
You may need to reboot. By the way, I've written drivers for Windows and OS/2 (yeah, I'm old) -- you don't want to do that, so enjoy the steps above.
Note 2: Initially, my UA-1000 was recognized but not outputting any sound. But once I did a factory reset on the UA-1000, it sprang to life. Resetting the UA-1000 is described on page 44 of the user manual which you can get from the same link above. Have fun!
I try to update my windows but I got this message:
I tried to reboot service but it didn't work.
Current version of my laptop: Version 1709 (OS Build 16299.192)
I am afraid this will be affected to future releases.
I recently had a similar problem on my PC and my laptop. My error code was as follows:
2018-08 Update for Windows 10 Version 1709 for x64-based Systems (KB4023057) - Error 0x80070643
After much kafuffle and reading quite a few articles and Microsoft waffle pages I decided to do it my own "straightforward" way. This is my story, if it helps you I am content. Summary:
Close/save all open applications;
Run Windows Update TroubleShooter;
Find the latest Cumulative Update;
Run the Cumulative Update;
Allow the computer to do the necessary restart processing.
The description below is what I did. It worked both times for me; firstly on my PC and secondly on my laptop. The difference with my laptop was that I didn't repeat the download of the Cumulative Update as I had already done this for the PC, I just ported the Update to the laptop via USB; everything else was the same.
On the laptop the whole process took about 40 minutes, start to finish. I didn't time it on my PC as I was doing things in slow stages. The download of the update is quite large (900Mb) so watch out for download charges if your ISP makes you pay for such things.
All descriptions/statements below apply solely to me. I am describing what I did and what I think. Like with Microsoft and others, any decision by you to follow any aspect of my description is entirely at your own risk. For any "lawyers" out there, any reference to "you" or implications that I am telling you what to do is just an unintended flaw in my poor English grammar.
Save and close all the applications that are being used:
The Cumulative Update will requires a restart of the computer so, for me, it was best to save any data now and close all the applications I had open in an orderly manner.
Find and run the Windows Update TroubleShooter:
Search the web for "Windows Update TroubleShooter". The page I ended up on was this:
https://support.microsoft.com/en-gb/help/4027322/windows-update-troubleshooter
Click the appropriate download link on this page. I am running Windows 10 (Version 1709; x64) so, for me it was: "Download Troubleshooter for Windows 10"; it was a small file, around 200Kb.
The download file was "wu170509.diagcab". I always "Save > Virus check > and then run".
Run the Troubleshooter (I double-clicked it);
On its first page, click "Advanced", then ensure "Apply repairs automatically" is checked, and finally click "Run as administrator". It reloads itself, click "Next" and let it run.
Whenever it found a problem I chose the "Apply this fix" option.
When it reports that it has completed, close the TroubleShooter.
This took me about 10 minutes to do (I am slow and I was also trying to make a cup of tea!).
Find the computer's details:
Load the Settings page; right-click the Windows "Start" icon -> Settings -> System -> About.
Note the following:
Under Device Specifications, note the System Type (mine is 64 bit "x64")
Under Windows Specifications, note the Edition, Version and OS Build details.
Find and run the Microsoft Update Catalogue:
Open a browser (mine is Internet Explorer) in Admin mode ("Run as Administrator" from its icon's Context Menu - I don't know why you have to do this but you get an error otherwise on IE);
Search the web for "Microsoft Update Catalogue"; the page I ended up on was this:
https://www.catalog.update.microsoft.com/home.aspx
Search for the latest Cumulative update for your version. I entered the following search terms that relate to my system in this year "2018 cumulative update windows 10 1709 x64";
Top of my returned list (the latest cumulative update) was:
2018-09 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4464217)
Note its KB number and click on its Title.
An "Update Details" window opens; click on the "More Information" link and a web page opens, mine was:
September 17, 2018—KB4464217 (OS Build 16299.666)
Verify the KB number with the Microsoft Catalog number just to make sure.
I only proceeded with this Update because its Build Number was greater than my current one (from section 3 above); for me, going backwards sounds like a route to a bigger mess.
Once I was content I was going forward I went back to the Microsoft Catalog (closing web pages and windows as necessary) and clicked the "Download" link for this Cumulative Update (KB4464217); a "Download" window appears. Click the link to download it (it says 863Mb). My download took 5 minutes via an Ethernet connection (no idea on timing regarding a WiFi download).
Run and check the Cumulative Update:
When the download had completed (and after virus checking it), I opened its folder and double-clicked the file therein and let it run. It took about 30 minutes to do its work. Once started it needed no help from me so I wandered off and did other work.
Once the Cumulative Update had completed I let it do its necessary restart. This is in fact a couple of restarts and took about another 10 minutes to complete.
Once these restarts had completed I loaded my system and did an immediate Windows Update. It returned with no errors and reported that my system was up to date - Yippee!
Notes:
A. There was one difference between updating my PC and laptop. On the PC my Desktop layout was undisturbed, on my laptop the Desktop layout was reset. I have no idea why the difference occurred.
B. In the middle of writing this, when I got to describing the Windows Update TroubleShooter, I decided to rerun the TroubleShooter on my PC. To my surprise it reported errors. I had done nothing of any significance since applying the Cumulative Update and checking it, just some simple Powershell stuff (Microsoft product) and a bit of internet browsing like news and football results (via Internet Explorer, another Microsoft product). It seems to me that Microsoft are screwing up their own Update System! What clever people they are - not.
Good Luck peoples - Pay It Forward.
The following Microsoft forum article suggests that it is a Windows Update glitch:
Update for Windows 10 Version 1709 for x64-based Systems (KB4041994) — error 0x80070643.
The article further suggests that the OP there has the later build of Windows, and that the problem may be suppressed by hiding the update (how-to provided in the linked article).
I am new in windows logo test . I heard this process from my friend . I created a application which consist of some drivers . so I need to sign from Microsoft for trusted installations of my software . I heard the windows logo process for sign my driver through some test conducted by me and need to send this report back to windows . So I have some doubt to setup this process .
How to setup this process ? (how many system needed ? and which OS I should install for testing) and what are the requirements ?
I think there is a server and client machine (So 2 system is needed ?) . How to setup this system ? can you provide step by step tutorials ?
Your understanding is correct. The testing goes by a few names, WHQL, hardware certification, logo test, etc. Just to give a few more keys words to google.
Microsoft outlines the steps that you need to take https://msdn.microsoft.com/en-us/windows/hardware/hh833792. Honestly, the process is not that bad all things considered:
Buy a code signing certificate. Microsoft lists who they support and there are plenty of discussions on the OSR forums that discuss signing requirements in great detail. We use Digitcert and have no issue. I recommend reading up on this article to make your life easier: http://www.davidegrayson.com/signing/. The whole cross-certificate detail is glossed over in the Microsoft docs.
Setup your company in the hardware dashboard. Pretty straightforward here; just follow the directions for uploading your code cert. Sign all the legal stuff and setup any other developers on your team if they need access.
Install the HCK. We bought the MSDN OS pack ($800 USD) just for the WHQL and it has been awesome. I used Server 2012 to run as the HCK server and installed it as a virtual machine on a pretty beefy PC. Runs great, no problems installing it, and configuration is intuitive. More details are here: https://msdn.microsoft.com/en-us/windows/hardware/jj123537.aspx
Configure your test PCs. I used a mix of VMs and physical PCs for this part. Going through the provisioning process is automated for the most part. I recommend taking VM snapshots once completed in case something goes south during testing.
The HCK server walks you through the tests you need to perform depending on the type of driver you are testing. For example, we are working on a printer so all of our testing involved printing.
We tested against XP SP3 all the way through Windows 8.1, both 32 and 64 bit though your needs may differ. We needed the driver in Windows update, not necessarily the hardware logo. Once completed we simply uploaded the passing report through the hardware dashboard and that was that.
It seems like a huge task but it is not the worst thing in the world so keep at it you will get it done!
I'm trying to use this Visual Studio extension for 2013, which recreates the built-in installer functionality from Visual Studio 2008/2010: http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx?CommentPosted=true&PageIndex=2#comments
It works, allowing me to edit the project as before. It has the install and uninstall commands when right-clicking the install project, too. It installs fine.
When I try to uninstall, though, I get the following error and then the uninstall rolls back:
Could not open key: HKEY_LOCAL_MACHINE32\SOFTWARE\Wow6432Node\Microsoft\
EAPSIMMethods\18\FastReauthContext. Verify that you have sufficient
access to that key, or contact your support personnel.
I am not doing anything with that registry key, and there don't seem to be any relevant results on google-- at least not in the normal top 5 pages. Does anyone know what causes this or how I can fix it?
While I am not able to uninstall, I am able to increment the version of the package and allow it to remove the previous install and install the new version (all at once) successfully.
I am using Windows 8.1 Pro 64 bit, the projects are compiled for <AnyCPU>, and the installer is configured for x86.
EDIT I am running Visual Studio as Admin. When uninstalling from the Control Panel, I am also clicking the 'allow' button in the UAC dialog window that pops up.
I know how to give myself access to a registry key (permissions). I want to know why this key is trying to be removed. I support this app on several machines and I don't want to have worry about remembering an uninstall hack in the future.
EDIT This only seems to be an issue for a 32x installer on a 64x OS or a Windows 8 issue. I was able to use the same 32x installer to successfully uninstall the app on a 32x Windows 7 machine.
This must be an environmental problem, that key doesn't have anything to do with installers. EAP-SIM is an authentication protocol for wireless networks. The FastReauthContext key almost surely was meant to avoid having to provide a username+password each time your machine reconnects to the network. Which makes the registry key content very sensitive of course, it can only be read by a service that runs with the System account.
So, something goofy going on with your networking setup. Verify that you can successfully reconnect to such a network. If you used a VPN before then make sure it is active again. Something like this. Update your question with anything that might be relevant to networking when you first installed the app.
I have had similar problem and what I found out this is caused by MSI attempting to delete whole "Software\Microsoft" section in the registry. Lucky you that it encounters this error and rolls everything back.
So the solution is the following:
Since you have installed your program whenever you try to uninstall it the system will run msi from cache that is usually located C:\Windows\Installer.
Find your package in the cache. Here is an article that may help you http://csi-windows.com/blog/all/27-csi-news-general/334-identifying-cached-msi-packages-in-cwindowsinstaller-without-opening-them
Open the package in Orca. You must do this as administrator.
Go to Registry table and find record with "Software\Microsoft" as a key. Most likely the Name column will contain either "-" or "*" value. This means that during uninstall MSI will try to delete whole "Software\Microsoft".
Either change the Name value to empty or "+" or try to change key to something like "Microsoft". The second option will cause that installer will not find the key to delete during uninstall, but it will skip this error and let you uninstall your program.
You installed an untested installer on your dev machine? Speaking from experience, don't do that! Snapshotted VM's are cheap and will save you from this sort of pain.
Visual Studio Deployment Projects (or VSI as it's now called ) is known for creating very poor quality installs. The combination of those two put you where you are today.
I would need to look at the full uninstall log and your MSI using ORCA to understand exactly what is going on. MSI Zap and a manual cleanup of resources is probably required at this point.