![]() ![]() tried with a policy but this prevent device to work) - but in this way everything is working and prolific driver will not be modified by windows. I am looking for something specific,(e.g. Then choose "No (your device might not work as expected)." this prevents to install any driver device automatically from windows update, so your driver will be not overwritten by windows. Navigate to Control Panel > System & Security > System > Advanced System Settings > Hardware > Device Installation Settings. Workaround i have found is simply install a working driver ( like your or anyone ), then disable windows update (only for drivers, this will not affect rest of updates) Yes, i can switch again to the correct driver as described ,or reinstall drivers. ![]() I have found also 3.9.1.0 version (I can share link if needed), but, again, after some time i found, in device section, "Please install corresponding PL2303 driver to support Windows 11" where i should have the COM port - I checked and looking version number 3.9.1.0 should be apparently a newest version but release date reporting August 2021( so again, windows trying to reinstall 3.8.40.0 :-) ) Hello, I using these drivers to connect my telescope with pc let me say unfortunately problem is that windows update soon will replace driver you installed with his lovely Prolific drivers 3.8.40.0, that works in win 10 but not in windows 11Īny version before 3.8.40.0 is working :-) as you said this one is, for win, the last one. July for the ones from the download page) and so Windows prefers it over them. The problem is probably that the non-working driver is the newest (September 2021 vs. I had only one other entry, a "ser2pl.inf" version " 3.8.40.0".ĭisconnect the device, and "pnputil /delete-driver oemXY.inf" with the INF file you located in the previous step.Ĭonnect the device again, and it should work, at least, it does for me. Then "pnputil /enum-drivers", and in the output look for Prolific drivers other than the ones from the previous step. It will add the two driver packages to the driver store and tell you what oemXY.inf files it has assigned to them. What I did is this:įirst install the downloaded driver by unpacking the zip file and "pnputil /add-driver *.inf /subdirs /install" (the /install is probably not necessary) from the extracted "Win11_DCHU" directory. Getting it installed is a bit tricky, it seems. There is a working driver at \_id=225&pcid=41, a bit down the page listed as "DCHU (for PC Vendors)". We will strive to maintain a fair, inclusive, and positive atmosphere, but we can't please all of the people, all of the time. Mods will remove posts and comments at their discretion for violating this.Ĩ. This includes callsign if they don't have it publicly displayed!Ħ. ![]() Do not post another user's personal information. Callsigns displayed must be your own callsigns.ĥ. Keep flair SFW and applicable to the hobby. Do not spam your product, website, blog, YouTube channel or other personal project.Ĥ. No personal attacks, hate speech, name calling, or discriminatory remarks allowed.ģ. Absolutely no military, paramilitary or militia use or discussion.Ģ. No illegal activity or advocacy for illegal activity. Post no individual sales See /r/HamFest Rulesġ. An unofficial source for everything related to Baofeng radios, and other similar modelsĪ sibling subreddit to /r/amateurradio No cross posting allowed to main ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |