Can't make changes inside System32/drivers

[mikephn]

I'm trying to automate an installation and I need to copy a new .sys to system32/drivers.

FileCopy and FileMove seem to make no changes, the file doesn't appear there after copying. Oddly enough, FileExists will tell me the file is there, when it's clearly not. The program that requires this .sys to be present also doesn't start.

I have all files visible, including system, and I'm requesting admin rights at the beginning of the script. I run Win7 64-bit.

So far I can only do it with a .bat being run by AutoIt, which is a bit pointless.

Can anybody offer a solution and/or explanation?

Many thanks

Mike

[gerwim]

Might be a stupid question, but what if you F5 in the folder? Sometimes Windows screws up and doesn't auto-refresh the folder.

[whim]

@mikephn

If your script runs/is compiled as 32-bits code, Win 7 will redirect ALL your 'operations' on system32 to sysWOW64 ...

So you might want to take a look there.

Extremely logical, isn't it ? (64-bit code in system32, 32-bits in sysWOW64)

HTH,

wim

[gerwim]

@mikephn

If your script runs/is compiled as 32-bits code, Win 7 will redirect ALL your 'operations' on system32 to sysWOW64 ...

So you might want to take a look there.

Extremely logical, isn't it ? (64-bit code in system32, 32-bits in sysWOW64)

HTH,

wim

This could be it too. To fix this, make your destination:

$dest = @WindowsDir & "\System32\Drivers\"

Edited October 19, 2010 by gerwim

[whim]

This could be it too. To fix this, make your destination:

True, but if you want to install 64 bit drivers, you might as well compile your script

as 64 bit - so it won't accidentally f*** up a 32 bit system.

whim

[mikephn]

The program that needs this .sys needs to have it in System32, and depending on the OS (64/32) I have two versions of the file to copy. I'm checking @OSArch to determine which one to copy, but the script needs to run on both 32 and 64 bit systems.

My path actually is based on the Windows directory, because I also noticed that the system directory AutoIt gives is for sysWOW64. So my command is:

FileCopy(@WindowsDir & "\System32\drivers\64b.sys", @WorkingDir & "\Win64\64b.sys", 9)

FileExists(@WindowsDir & "\System32\drivers\64b.sys") returns 1, but the file is not there. It also doesn't appear in sysWOW64.

[whim]

@mikephn

You will also need full Administrator rights to write to /drivers, when running from SciTe add:

#RequireAdmin

to the top of your script.

In a compiled script, use

#AutoIt3Wrapper_res_requestedExecutionLevel=requireAdministrator

hope that helps,

whim

[trancexx]

This is only (un)proper redirection, nothing more. Use functions for disabling/enabling redirection an all should work fine.

String \System32 is interpreted differently depending on... what it depends.

[mikephn]

This is only (un)proper redirection, nothing more. Use functions for disabling/enabling redirection an all should work fine.

String \System32 is interpreted differently depending on... what it depends.

The line is:

DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

Worked like a charm. Thanks a lot everyone!

[llewxam]

The line is:

DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

Worked like a charm. Thanks a lot everyone!

Sorry to necro-post a little, but this helped me SOOO much that I had to acknowledge it!! I was trying everything reasonable, then some and some dumb stuff too like trying to set attributes and taking ownership before finding that FileGetSize was returning 0! The above DllCall made everything fall in to place!

BTW, Win7 x64

THANKS!!!!!

Ian

[ViciousXUSMC]

I'll Necro it again Just fixed my issue.

So strange as I was doing a filecopy and not using any macros I was using a defined file path.

In this case my code:

#RequireAdmin

;Disabled Auto Push to 32bit Location
DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 1)

FileInstall("C:\My Places\Scripting\AutoIT\My Scripts\Disable Flash Update\mms.cfg", @TempDir & "\mms.cfg", 1)

If FileExists("C:\Windows\SysWOW64\Macromed\Flash\") Then
    FileCopy(@TempDir & "\mms.cfg", "C:\Windows\SysWOW64\Macromed\Flash\mms.cfg", 1)
Else
EndIf

If FileExists("C:\Windows\System32\Macromed\Flash\") Then
    FileCopy(@TempDir & "\mms.cfg", "C:\Windows\System32\Macromed\Flash\mms.cfg", 1)
Else
EndIf

Just a little script to push the mms.cfg file to disabled auto updated on Adobe Flash.

My question now is this, are there any ill effects in running that dllcall, like do I need to re-enable it after I have finished my script?

Edited February 9, 2015 by ViciousXUSMC