I would make a backup and then upgrade to 10, if something does not work you can go back within windows, but if everything fails you have the backup. I think win 10 is absolutely great and after many updates it outperforms win7. I can recommend it absolutely. And later o would make a fresh install of win 10, this is always better, but an upgrade will do also for some time.
Turns out you have to enable testing mode in Win7 to use driver that is not crossed signed. So scratch that. What about the VHLK, can that be used to create whatever is needed to get Win7/Vista driver signed? I read somewhere that the HCK/HLK method would end Jan 2023, so I don't want to waste my time with all the complicated stuff when all I want to do is sign something. Would me setting up another system with the date set way back to sign things without a timestamp work or is a signed timestamp needed? Or better, can someone convince MS to add the tick boxes for the catalog to support vista/win7 (and server equivalents) - It's the same driver that works in Win10. Also be nice to allow SHA1 for older OS (signed MS SHA1) - since all the new Windows versions ignore SHA1 anyway, generating one for old OS that needs them isn't a security issue. That would solve everything!
I'm pretty sure this will NOT work. if i remember correctly Ion (win7) has 2 DVI-D ports. they output digital signal. but regular DVI-VGA adapter usually have a DVI-I or DVI-A which transports analog signal. i think you can't even plug your adapter into the Ion because the adapter has the four additional pins (that are used to transport the analog signal), but the DVI-D on the Ion doesn't have the four holes for it (and also doesn't produce the analog signal).
I recently attempted to open my project on a different PC that has a lower version of UiPath Studio Enterprise installed. This error occurred during the debugging process.
It seems that the package runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets is not being found in any of the specified sources: C:\Actimai\Packages, C:\Program Files\UiPath\Studio\Packages, Connect, , , Local, LocalPackages, Official.
so "3072 bit" seems hit the problem. how can I make win7/eset agent accept it? I already installed a hundred win10 machines with the certificate. I don't want to reinstall these win10 to use a new certificate if possible.
then I try a simpler method, I transform the exported AES-256-CBC pfx to another format which win7 will accept. I modify the agent installation config file to use the new pfx and fortunately the installation procedure swallow it then everything seems become normal.
and since openssl 3.0 is coming to every linux distribution, I think eset-protect should modify the openssl pfx export parameter as soon as possible. it seems a one-line thing to support win7 under openssl 3.0.
ok. the agent certificate is stored at mysql database under tbl_certificates table. replace the agent "certificate_pfx_blob" column with the transformed pfx then eset-protect can create an all-in-one installer suitable for win7.
I gave my son my laptop which left me with my old win7 32 bit toshiba. where do i download the 32 bit cura?my computer says its incompatible with the 64amd. any possible way someone can leave the link. im a bit overwhelmed atm so my mind is a bit jumbled
dd2b598166