Help running a driver installer in Post-Setup and disable a pesky OneDrive notification in Windows Defender

[xShARkx]

Hello everybody,

I am trying to run a driver installer silently in post-setup for a fingerprint reader, and also disable a pesky one drive notification that keeps coming up in windows defender.

1 - First let's begin with the driver installer for the fingerprint reader, the driver installer, requires an ".iss" file to run with the installer to install it silently as per screenshots below...

The files you get when you download the driver for the fingerprint reader from the manufacturer's website:

It comes with a .bat for silent install, inside this bat we have:

It calls the already mentioned .iss file for silent install, and here is what is inside it:

How to approach this in post-setup in ntlite? I tried something's, but nothing worked.

Download of the files\driver from the manufacturer's website:

Official link → https://drive.google.com/file/d/1F3_qzMm5QgbpgyhK4Yq02xJ8SsTyKTfA/view

https://unionbiometrics.com/en/portfolio/hamster-x/

It's at the bottom of the page, in case you want to check the download link yourself, instead of trusting the link shared by me.


PS: I can't just extract the driver from the installer and import it in ntlite's driver section, because I've tried that already and even with the device showing up properly in device manager, it did not work! I tried the software that I need the fingerprint to work with and nothing, tried other software programs too and nothing, but as soon i as run the fingerprint reader driver installer without even removing the imported driver that I've added in ntlite, everything works.


2 - I am trying to get rid of this pesky one drive notification that keeps showing up in windows defender:

Any idea how? I tried searching for the answer on the forum, but It's so hard because of the key word "one drive", so many threads with not what I want, just because of the word one drive.

Thank you!

 

[garlin]

1. Why does the "x64" script run the x86 version of the installer? This error is repeated in each of the "x64" batch files:

@echo off
pushd "%~dp0"
UBio_Hamster_X_Driver_Setup_x86.exe -s -f1"%~dp0install_UBio_Hamster_X_Driver.iss"

Dual-architecture script:

@echo off
pushd "%~dp0"

if not "%PROCESSOR_ARCHITECTURE%" == "AMD64" (
    UBio_Hamster_X_Driver_Setup_x86.exe -s -f1"%~dp0install_UBio_Hamster_X_Driver.iss"
) else (
    UBio_Hamster_X_Driver_Setup_x64.exe -s -f1"%~dp0install_UBio_Hamster_X_Driver.iss"
)

2. Supposedly enabling "Controlled Folder Access" will make the Security Center warning disappear. Though it can create weird side effects with folders that don't allow writes.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender\Windows Defender Exploit Guard\Controlled Folder Access]
"EnableControlledFolderAccess"=dword:00000001

 

[xShARkx]

1. Why does the "x64" script run the x86 version of the installer? This error is repeated in each of the "x64" batch files:

I have no clue, I've only noticed now that you mentioned, because I've actually downloaded my driver which is the same as the one above, from a Brazilian website which sells these types of devices and in that version, everything is correct as you can see below:

But since the Brazilian site requires a login to download the driver, I went after the manufacturer website so I could share it here straight from there because I know accessing a link from a stranger can be sketchy.

I guess the Brazilian website, guys, downloaded the driver from the manufacturer and fixed the bat files.

Dual-architecture script:

@echo off
pushd "%~dp0"

if not "%PROCESSOR_ARCHITECTURE%" == "AMD64" (
    UBio_Hamster_X_Driver_Setup_x86.exe -s -f1"%~dp0install_UBio_Hamster_X_Driver.iss"
) else (
    UBio_Hamster_X_Driver_Setup_x64.exe -s -f1"%~dp0install_UBio_Hamster_X_Driver.iss"
)

Thx for the dual architecture bat file, but how do I add this to Post-Setup in ntlite (driver installer + .iss file for silent install), because I want to run this driver installer in post as explained above since the device will only work properly when I run the installer while extracting and importing the driver in ntlite won't do.

 

[garlin]

More like the Brazilians copied them without paying attention. The x86 and x64 folders have identical files, except for the EXE. They could have just made one folder, and wrote a dual-architecture script or two sets of named x86/x64 scripts.

1. Add / Directory -> UBio folder
2. Add / Command / Before logon (Machine) -> "%SYSTEMROOT%\Setup\UBio_Hamster_X_Driver_1.4.0.0\install_silent.bat"

Basically you're copying the long folder path NTLite provided you in the Copy line's Parameters column, and using that to find the batch script.

 

[xShARkx]

More like the Brazilians copied them without paying attention. The x86 and x64 folders have identical files, except for the EXE. They could have just made one folder, and wrote a dual-architecture script or two sets of named x86/x64 scripts.

What I meant, is that in the Brazilian version of the .bat files are calling the right .exe, in other words, the .bat files inside the x64 folder are calling the x64.exe correctly while the .bat files inside the x64 folder from the manufacturer website is calling the x86.exe like you've pointed.

They just downloaded the files from the manufacturer website, fixed the .bat to call the right .exe file and that was it, but like you've said, they could have done the dual-architecture script which checks the installed system and selects the right .exe file.

TBH I did not even look at the x86 folder, did not even know the files were the same besides the .exe, because I am running x64 images only.

1. Add / Directory -> UBio folder
2. Add / Command / Before logon (Machine) -> "%SYSTEMROOT%\Setup\UBio_Hamster_X_Driver_1.4.0.0\install_silent.bat"

Basically you're copying the long folder path NTLite provided you in the Copy line's Parameters column, and using that to find the batch script.

View attachment 14802

Thank you very much, it works!



Another question, is there any log on the image itself after it's done installing regarding post-setup silent installations? Or somewhere else?

Asking because I just need to run one last driver installer in post-setup and the parameter for its silent installation is just /S according to the manufacturer documentation, so I've tested it in windows, and it works! But when I add the installer to post-setup using the /S parameter for silent install, it does not work... I go to Control panel → Programs and Features to check and see if it installed and it's not.

The driver installer is for a pinpad, this one:

https://ingenico.com/en/resources/ingenico-usb-driver-application-and-installation-guide

thank you!

 

[garlin]

Another question, is there any log on the image itself after it's done installing regarding post-setup silent installations? Or somewhere else?

That depends on the installer app. Some installers will create a log file, others only send output to the screen. If they print to the screen you can redirect the output by appending "2>&1 \path\to\logfile.txt" at the end of the Post-Setup command line.

Asking because I just need to run one last driver installer in post-setup and the parameter for its silent installation is just /S according to the manufacturer documentation, so I've tested it in windows, and it works! But when I add the installer to post-setup using the /S parameter for silent install, it does not work... I go to Control panel → Programs and Features to check and see if it installed and it's not.

The driver installer is for a pinpad, this one:

https://ingenico.com/en/resources/ingenico-usb-driver-application-and-installation-guide

Some installers do care about capital letters. /s doesn't run in silent mode. /S works.

It can also be called via the command line with the following parameters which are case sensitive:

 

[xShARkx]

That depends on the installer app. Some installers will create a log file, others only send output to the screen. If they print to the screen you can redirect the output by appending "2>&1 \path\to\logfile.txt" at the end of the Post-Setup command line.



Some installers do care about capital letters. /s doesn't run in silent mode. /S works.


View attachment 14809

Yes, I saw the instruction about the case-sensitive /S on the documentation, but still does not work in ntlite post-setup, only in windows it works, here:

In windows, it works, but here even using /S instead of /s, does not work.

Everything i got on my post-setup, just in case something else is causing this:

 

[xShARkx]

That depends on the installer app. Some installers will create a log file, others only send output to the screen. If they print to the screen you can redirect the output by appending "2>&1 \path\to\logfile.txt" at the end of the Post-Setup command line.



Some installers do care about capital letters. /s doesn't run in silent mode. /S works.


View attachment 14809

Ok, it seems to work now! I had to add it to after logon instead of before logon.