Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Jody Thornton

MSE For Vista Now Shows XP Nag Screens

Recommended Posts

Posted (edited)
13 hours ago, VistaLover said:

... But @dencorso did provide usage hints:

When you unpack the attachment, you'll find a wget.exe binary; the way the batch file is written, wget.exe needs to be in your %PATH% (... environment variable, read more in Wikipedia ); if you don't want to manually add it to %PATH%, you can place that binary inside a directory already in %PATH%: @dencorso's suggestion was

%windir% = %SYSTEMROOT%

which should default to "C:\Windows", if your OS is indeed installed in the C drive...

The second line of the .cmd file changes your working directory to your %TEMP% folder ("Temporary Files" folder, should default to "C:\Users\<YourUserName>\AppData\Local\Temp"), where, of course, there's no wget.exe to be found :


pushd %temp%

This is why it is imperative you place wget.exe in a directory Windows already has in %PATH%, so it would know where to invoke it from...

Apologies for possibly sounding a bit harsh (... rest assured I mean well), but, unless you have some sort of learning disabilities (which if true, I profusely apologise for), almost everything new one wants to learn about is already there in the web, accessible with a bit of searching... :)

Hope I've helped!

I've cut and pasted them into the Windows folder and that seems to work, I then put a shortcut to the MSEUPD_Vista.cmd file onto the desktop for easy updating.

12 hours ago, Vistapocalypse said:

Have you even tested your real-time protection at AMTSO? I am now using a third-party antivirus because there is more to online security than getting pretty green colors in your 6-year-old MSE client.

 

I'm just using it on this older laptop as its lightweight and doesn't use up much system resources unlike some I've used in the past.

Which lightweight modern alternative would you recommend? I know most people would say to upgrade to Windows 7 at-least, but to be honest its a bit of a hassle for a secondary machine.

Edited by crazyal12

Share this post


Link to post
Share on other sites

2 minutes ago, crazyal12 said:

I've cut and pasted them into the Windows folder and that seems to work, I then put a shortcut to the MSEUPD_Vista.cmd file onto the desktop for easy updating.

... Only wget.exe needs to be in %PATH%; hence, you could have left the batch file (*.cmd) inside a directory of your choice (or place it on the desktop); but whatever tickles your fancy... ;)

Share this post


Link to post
Share on other sites
2 hours ago, crazyal12 said:

I've cut and pasted them into the Windows folder and that seems to work, I then put a shortcut to the MSEUPD_Vista.cmd file onto the desktop for easy updating.

That's perfect. There's no need to change anything from what you've done

2 hours ago, VistaLover said:

... Only wget.exe needs to be in %PATH%; hence, you could have left the batch file (*.cmd) inside a directory of your choice (or place it on the desktop); but whatever tickles your fancy... ;)

Yes. But do *not* fix what isn't broken. Let things stay as they are. :cool:

2 hours ago, crazyal12 said:

I'm just using it on this older laptop as its lightweight and doesn't use up much system resources unlike some I've used in the past.

Which lightweight modern alternative would you recommend? I know most people would say to upgrade to Windows 7 at-least, but to be honest its a bit of a hassle for a secondary machine.

I do recommend it precisely because it's lightweight and unobtrusive. I've used it on my main machine since Oct 2016, when Avast took over AVG and suddenly decided to EoS all versions of AVG but the latest. Up to then I had been using (paid) AVG 2011 which, with various things turned off was reasonable IMO for use. In fact I've never got any malware in any of the machines I use/mantain, since before 2001. However, I did get a prufusion of false positives with AVG, along this time, and none at all with MSE. It's too bad I cannot keep using it anymore on XP... fact is most of my machines running XP (I've got 5) nowadays are powerful enought to do it using MBAM 3.5.1.2522, but for my Eee PC 900 (a single core Celeron M 353 ULV @ 900 MHz machine), which for now remains just with the unupdatable MSE, while I think what to do...

In any case, my 2¢ is: too much paranoia is bad for the user's health and does not make your machine safer, but does slow it! YMMV, of course.

Share this post


Link to post
Share on other sites
Posted (edited)
On 7/23/2019 at 7:59 AM, dencorso said:

That batch was offered as an example, to be tweaked as needed.

... In the good ol' days :P (prior to July 2019) when Windows Defender in Vista would receive definitions updates via Windows/Microsoft Update, WU would create a System Restore Point before installing the new definitions file; that SRP would be named "Windows Defender Checkpoint" (or something similar, memory fails me now... :blushing: ) and those automated restore points had saved my "behind" when I wanted to revert some unwanted/inadvertent change on my machine.

I have also the following setting checked:

IwBG38M.jpg

but this is only to revert changes applied by WD (and I always have to "Permit" them myself beforehand...).

Unfortunately, and I understand this is highly unwise, I'm not in the habit of creating manual restore points in a frequent schedule; of course, the OS itself would create one when it thinks it's needed, however I have found this task to be performed in a very fickle fashion; :angry: with me not receiving Windows Updates anymore, and not installing/uninstalling applications that often, I've found that it may take the OS many days to auto-create a RP...

So I looked into ways of implementing the automated creation of a SRP alongside the automated (but manual!) update of WD via my WDUPD_Vista.cmd batch file, inspired by its MSE counterpart kindly offered by @dencorso (few posts previously...).

Research has landed me on

https://www.winhelponline.com/blog/create-system-restore-point-script-windows-10-8-7-vista-xp/

and their VBScript linked to in their "Method 3: Restore Point creation using Script" (slightly modified by yours truly!):

'""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
'Script to create a System Restore point in Windows 10, 8, 7, Vista and XP
'Created on May 10 2008 - Revised on Oct 13 2016
 2008-2016 - Ramesh Srinivasan. http://www.winhelponline.com/blog
'""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
If GetOS = "Windows XP" Then CreateSRP
If GetOS = "Windows Vista" Or GetOS = "Windows 7" Then
	If WScript.Arguments.length =0 Then
  		Set objShell = CreateObject("Shell.Application")
		objShell.ShellExecute "wscript.exe", """" & _
  		  WScript.ScriptFullName & """" & " uac","", "runas", 1
	Else
  		CreateSRP
  	End If
End If

If GetOS = "Windows 8" Or GetOS = "Windows 10" Then
	If WScript.Arguments.length =0 Then
  		Set objShell = CreateObject("Shell.Application")
		objShell.ShellExecute "wscript.exe", """" & _
  		 WScript.ScriptFullName & """" & " uac","", "runas", 1
	Else
		const HKEY_LOCAL_MACHINE = &H80000002
             	strComputer = "."
            	Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
             	strKeyPath = "SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore"
             	strValueName = "SystemRestorePointCreationFrequency"
             	oReg.SetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName, 0  
  		CreateSRP
		oReg.DeleteValue HKEY_LOCAL_MACHINE, strKeyPath, strValueName
  	End If
End If

Sub CreateSRP
	Set SRP = getobject("winmgmts:\\.\root\default:Systemrestore")
	
	If GetOS = "Windows 10" Then
		sOut = SRP.createrestorepoint ("Manual Restore Point", 7, 100)
	Else
		sDesc = "Windows Defender Update Restore Point"
		If Trim(sDesc) <> "" Then
			sOut = SRP.createrestorepoint (sDesc, 0, 100)
		End If
	End If
		
	If sOut <> 0 Then
		WScript.echo "Error " & sOut & _
		  ": Unable to create Restore Point."
	End If
End Sub

Function GetOS    
    Set objWMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
    	".\root\cimv2")
    Set colOS = objWMI.ExecQuery("Select * from Win32_OperatingSystem")
    For Each objOS in colOS
	strOSName = objOS.Caption
        If instr(strOSName, "Windows 7") Then
        	GetOS = "Windows 7"    
        ElseIf instr(strOSName, "Vista") Then
        	GetOS = "Windows Vista"
        ElseIf instr(strOSName, "Windows XP") Then
      		GetOS = "Windows XP"
	ElseIf instr(strOSName, "Windows 8") Then
      		GetOS = "Windows 8"
	ElseIf instr(strOSName, "Windows 10") Then
      		GetOS = "Windows 10"
        End If
	Next
End Function

Of course, I then had to visit

https://stackoverflow.com/questions/11899730/running-vbscript-from-batch-file

to learn how to incorporate this in my batch file...

The important thing here is that the SRP creation be fully completed prior to wget (finishing) downloading file mpas-fe.exe (or perhaps prior to file mpas-fe.exe being executed).

I am torn between two variants:

@echo off
start /min /wait cscript "create_restore_point.vbs"
if not exist mpas-fe.exe start /min /wait wget -O mpas-fe.exe https://definitionupdates.microsoft.com/download/DefinitionUpdates/x86/mpas-fe.exe
if exist mpas-fe.exe start /min /wait mpas-fe.exe 
del mpas-fe.exe

and

@echo off
cscript "create_restore_point.vbs"
timeout /t 15 /nobreak
if not exist mpas-fe.exe start /min /wait wget -O mpas-fe.exe https://definitionupdates.microsoft.com/download/DefinitionUpdates/x86/mpas-fe.exe
if exist mpas-fe.exe start /min /wait mpas-fe.exe 
del mpas-fe.exe

where file create_restore_point.vbs is placed adjacent to the .cmd script.

@dencorso, your opinion on this would be highly appreciated (along with any other alternative you might be able to suggest ;) ); many thanks in anticipation :wub:

Edited by VistaLover

Share this post


Link to post
Share on other sites

start  /min  /wait  causes a new CMDBox to be opened, minimized (viz. /min) and the command to be run inside this new CMDBox, while causing the original CMDBox to wait for this command to finish (viz. /wait), before going on to the next command (= next line). So the 1st scrip guarantees the .vbs run by cscript has finished before running wget and that wget has finished (which is fundamental) before attempting to run mpas-fe and that it also has finished, before deleting it. So one can be sure things will happen in the desired (and needed) order.
The second script, OTOH, starts the .vbs and waits 15 seconds before proceeding. But in highly multitasking systems as the NT-OSes are, one cannot really be sure that 15s will always be enough. So I think the 1st script is best. My 2¢ only, of course.

Share this post


Link to post
Share on other sites
14 hours ago, dencorso said:

So one can be sure things will happen in the desired (and needed) order.
(snipped)
So I think the 1st script is best.

Thanks :wub:

14 hours ago, dencorso said:

The second script, OTOH, starts the .vbs and waits 15 seconds before proceeding. But in highly multitasking systems as the NT-OSes are, one cannot really be sure that 15s will always be enough

... So, it may well be just a case of increasing the time interval to, say, 45 or 60 (sec) ? Anyhow, first variant it is then... :cool:

Share this post


Link to post
Share on other sites

The point is any guess to what "enough" is has some chance to be wrong in some unforeseen situation, once in a blue moon... OTOH, "until it ends" may vary widely, but *never* fails. In fact this is more a philosophic question than an actual one, it all depends on whether failing in, say, 0.001% of the time is good enough or a deal breaker. :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...