New
#321
@Matthew Wai I showed your solution to the non-english path name problem to @rpo at MDL forum who wrote the vbscript portion of the wrapper script code (I'm a horrible vbscript programmer and can only make modest edits, I only know batch script) so he came up with this solution ("%~dp0" was not the problem after all):
In wrapper script 2.5.5 change this code in lines 337 and 410 (change highlighted in blue)
to thisCode:echo Set Fso=CreateObject^("Scripting.FileSystemObject"^):Set f=Fso.CreateTextFile^(fso.GetSpecialFolder^(2^) ^& "\task.xml",True^)
The script now works in any language path name. Thank you for the pointers. Your input is much appreciated.Code:echo Set Fso=CreateObject^("Scripting.FileSystemObject"^):Set f=Fso.CreateTextFile^(fso.GetSpecialFolder^(2^) ^& "\task.xml",True,True^)
@pf100
I've been studying the WUMTWrapperScript.
I notice that you have a section::Determine if running 32 or 64 bit Windows OS and set variables accordingly
- but what you then seem to check is the CPU architecture not the Type of the OS itself
- whereas you could use something like If Defined ProgramFiles(x86) (Set OSType=x64) Else (Set OSType=x86) to achieve the stated aim because that system variable only exists on 64-bit Windows.
Or am I missing the point of that part of the script?
What I am doing is not as ambitious as your scheme.
- I already routinely set my connections as metered [manual procedure] & I inhibit USOClient [batch file]
- I also already have a startup batch file [well, logon, actually - because it needs Admin access] that checks that the connections & USOClient remain as intended
So I am working my way through each of your identified update hijackers to add them to both my inhibiting batch file and my checking batch file. I have been getting away with just using my existing precautions so far so my other jobs are currently higher priority but I am very grateful for the work you have done in identifying these other villains.
Yours,
Denis
Thanks @Matthew Wai will do. Sorry I didn't get a notification for this post.
The administrator has added a new option to completely disable Windows Update.
Enable or Disable Windows Update Automatic Updates in Windows 10 | Tutorials
I'm checking the architecture of the OS.
I decided early on to not check for "Program Files (x86)" because some programs are hard-coded to install in that folder and will create it if it doesn't exist even on a 32 bit OS and so is not a reliable way to check the OS's architecture.
If you want to find the architecture of the OS:
Vista and newer:
wmic os get osarchitecture
Xp and newer:
wmic cpu get AddressWidth (this is how I check)
If you want to find the architecture of the processor itself:
wmic cpu get DataWidth
Source.