Search the Community
Showing results for tags 'updating'.
Good Afternoon all, I know there is some logic when updating the source files for an application that can differentiate installing onto a 32 bit system or a 64 bit system, and also that there are detection methods to determine if something is installed. What I would like to know (or if anyone has done this) is how you can appropriately use logic to determine which software to install. Here's the example scenario if I lost anyone: Computer A is 64-bit Windows 10 and has 32-bit installed Mozilla Firefox 51 Computer B is 64-bit Windows 10 and has 64-bit installed Mozilla Firefox 51 Since computer A has 32-bit Firefox installed, go ahead and install 32-bit Firefox 54 Since computer B has 64-bit Firefox installed, go ahead and install 64-bit Firefox 54 I haven't tried this myself yet, but I didn't want to go down the rabbit hole and get lost. I have been able to successfully deploy a 32-bit and 64-bit application that uses the logic "Windows X 32-bit" and "Windows X 64-bit" to differentiate based upon processor architecture, but I don't believe the same concept will work here. Thanks!
Hi, I have a question regarding surface pro device firmware. We deploy Surface Pro 3s and Pro 4s at our entity. When a new driver/firmware pack is released from MS, we follow the usual instructions in downloading and applying the new driver/firmware pack to the devices. My question however is this- I noticed that if I run a manual windows update on either the surface pro 3 or pro 4, I see another system hardware update within the Windows update menu, when I know we have completed importing the newest drivers/firmware. Does anyone know why this is? I am guessing it is related to the touch panel itself, but I am looking to confirm. thanks.