Microsoft System Sweeper

[Roderunner]

Did you read the first paragraph on my image ?

 

[marsmimar]

As I posted in post #3 the program didn't run on my PC. It stopped with an error message after installing the necessary Windows files.
Is the possible reason for this behaviour that I'm running a German Windows version?

I haven't looked at Sweeper so it's possible the Beta doesn't support all languages yet. Just out of curiosity, is your operating system called Microsoft Fenster?

 

[Bonni24]

You are kidding?

 

[Acgdickie]

Wow, I work in a school and the kids come in all the time with spyware and viruses, am always looking for something new should get a kid in before the end of the week so will try and will let you all know how it goes.

Also on a side note it is good to hear that Microsoft are going to even more ends to stop crap on windows, I find the biggest complaint from kids about windows (bar from not being Mac) are the viruses. Even though windows 7 with a virus scanner and defender has improved things greatly there are still major issues and all of there work helps.

 

[borg6]

Dell Speedstep

I had the same problem with a Dell Optiplex 745, other 745's worked fine. I compared the BIOS settings and found that the 745 that set the error code had the Speedstep turned on. After turning Speedstep off... no worries program ran fine.

 

[alphanumeric]

I noticed the mpam-fe.exe file in the root of my drive and thought that looks familiar. It appears to be the Microsoft Security Essentials definitions file. If so you my be able to just download the latest from here > Get the latest definitions - Microsoft Malware Protection Center < and just replace that one file instead of formating your thumbdrive every time you want to update it. I compared the details tab under properties to a definitions file I downloaded today and they are a perfect match. Its mpam-fe64.exe for the 64 bit version.

 

[Brink]

I noticed the mpam-fe.exe file in the root of my drive and thought that looks familiar. It appears to be the Microsoft Security Essentials definitions file. If so you my be able to just download the latest from here > Get the latest definitions - Microsoft Malware Protection Center < and just replace that one file instead of formating your thumbdrive every time you want to update it. I compared the details tab under properties to a definitions file I downloaded today and they are a perfect match. Its mpam-fe64.exe for the 64 bit version.

Nice find Kerry.

In addition though...


When running the Microsoft Standalone System Sweeper Tool again on the same USB flash drive, if the following conditions below are met, the tool will only download definitions (approx. 60MB) and update the USB drive without reformatting it.

The USB flash drive has Standalone System Sweeper previously installed on it.
The Microsoft Standalone System Sweeper Tool version that was used to create the bootable USB flash drive the first run is the same as being used for the second run.
Files on the USB flash drive are not damaged or missing (the tool will verify that).

 

[gmorphus]

Sounds like Microsoft is getting even deeper to stop the bad things from happening. If it still happens, a free tool to help you out. Yes it's in Beta, but doesn't most things start that way? I would like to thank all those who use Beta and all the testing so the rest of us get a great program.

I'd like to join in the thanking whoever tried the beta of the Microsoft Standalone System Sweeper Tool!

I downloaded and installed the x64 on a USB drive and scanned. Worked out fine.

Although even though it says it just needs 250MB worth of space on a USB drive (which kind of implies it doesn't need to format it), it still needed to format the USB drive even though the drive was already bootable. So that was a little misleading...

I will pass your comment to support Airbot - thanks.

...Maybe I'm a little short on basic PC knowledge. When I installed the program to the USB drive, it was "F", and I chose to scan "C". When the scan ran it was scanning drive "E", is this normal? Whatever drive the system boots from is considered C:\?

Britton, the drive letter of your mounted USB drive, nor the drive letter of your already installed operating might different when booting off the USB drive create by the tool.
Hope that helps.

As I posted in post #3 the program didn't run on my PC. It stopped with an error message after installing the necessary Windows files.
Is the possible reason for this behaviour that I'm running a German Windows version?

Bonnie24, your error is not related to having run wrong configuration as Brink suggested. Since this is on beta and not fully supported yet, we'll try to have a look at it soon but I can't commit to anything.
Also, please make sure you are using the latest release of this beta, as downloaded from Microsoft's connect site.

I had the same problem with a Dell Optiplex 745, other 745's worked fine. I compared the BIOS settings and found that the 745 that set the error code had the Speedstep turned on. After turning Speedstep off... no worries program ran fine.

Thanks borg6. I'll pass this bit of info to support.





Please note that this is not an official support forum for the Microsoft Standalone System Sweeper tool. Solutions to issues with Microsoft products can be found here.
The information I provided in this post is relevant for version 1.0.856.0 of the tool.
I just happen to pass through this forum and providing assistance out of good will.
I'd like to thank you all for trying out Microsoft's beta release of this tool - it's greatly appreciated.
This tool's official beta page can be found at Microsoft's Connect site.

Thanks,
Guy Arad.

 

[alphanumeric]

I noticed the mpam-fe.exe file in the root of my drive and thought that looks familiar. It appears to be the Microsoft Security Essentials definitions file. If so you my be able to just download the latest from here > Get the latest definitions - Microsoft Malware Protection Center < and just replace that one file instead of formating your thumbdrive every time you want to update it. I compared the details tab under properties to a definitions file I downloaded today and they are a perfect match. Its mpam-fe64.exe for the 64 bit version.

Nice find Kerry.

In addition though...


When running the Microsoft Standalone System Sweeper Tool again on the same USB flash drive, if the following conditions below are met, the tool will only download definitions (approx. 60MB) and update the USB drive without reformatting it.

The USB flash drive has Standalone System Sweeper previously installed on it.
The Microsoft Standalone System Sweeper Tool version that was used to create the bootable USB flash drive the first run is the same as being used for the second run.
Files on the USB flash drive are not damaged or missing (the tool will verify that).

I have to admit, I just downloaded it to play with and didn't read though all the documentation. I also downloaded the latest versions for the Safety Scanner, Malicious Software Removal Tool, and MSE definitions, at the same time. Otherwise I probably wouldn't have noticed the mpam-fe file. I was thinking it would be kind of hard on your flash drive if it formated it every time you updated it. Looks like Microsoft thought of that too,

 

[johnwillyums]

I just downloaded the x64 bit version to a USB drive. I have 3 hdds, 2 with Windows on and a whole drive with Linux Mint on. So I press F12 once "only boot choice" and choose either my Windows Drive or Linux.
When I tried to boot the system sweeper USB stick nothing happened for a while-black screen-and then Linux booted. Hey ho.

 

[alphanumeric]

I just downloaded the x64 bit version to a USB drive. I have 3 hdds, 2 with Windows on and a whole drive with Linux Mint on. So I press F12 once "only boot choice" and choose either my Windows Drive or Linux.
When I tried to boot the system sweeper USB stick nothing happened for a while-black screen-and then Linux booted. Hey ho.

Did you run the downloaded file or just copy it to your flash drive? You need to run it to create the bootable flash drive.

http://www.sevenforums.com/tutorials/166445-microsoft-standalone-system-sweeper.html

 

[Skulblaka]

Alright, I've completed the scan on my cousins infected computer. The scan detected the exact cause and cleaned out, it was perfect, no traces of the virus left.

This is a really useful tool, I'm keeping it on my USB.

 

[johnwillyums]

Yes, I ran it and chose to install on USB stick. It completed the install. I then set a boot choice for the USB but, as I say, after a while it booted Linux. It'll be GRUB grabbing the boot I reckon.

 

[alphanumeric]

Yes, I ran it and chose to install on USB stick. It completed the install. I then set a boot choice for the USB but, as I say, after a while it booted Linux. It'll be GRUB grabbing the boot I reckon.

If you set your boot order to the thumbdrive first grub shouldn't be able to, as you say, grab the boot. It might be coded so that if it doesn't detect a windows operating system it doesn't run and exits out. It might have just looked at the boot loader/active partition and saw that it wasn't windows. Just my best guess, it worked fine on my 64 bit windows 7 PC and my 32 bit XP PC.

 

[johnwillyums]

Both the Windows and the Linux install are on different HDDs so they are both active. As I say, I make the choice between which to run using F12 on the BIOS.
When I've done dual boot using more traditional methods GRUB always takes precedence. So you have to choose Windows in GRUB and then select it again in Winboot.
So I imagine that, with a boot choice set to USB, System Sweeper starts and sees GRUB as it is more powerful. As it cannot detect Windows, as you say, it doesn't do anything.
If I get any problems I could always just disconnect the Linux drive physically, I imagine this would work but I don't think I'll try it right now as everything is running smoothly.

Thanks for your input alph

 

[mickey megabyte]

it might not be grub at all.

on my machines, if i want to boot from a usb stick, i have to go into bios and change the hard disk boot priority order, as the usb drives are usually seen as low priority hdd's.

ymmv...

 

[johnwillyums]

Hi Mickey Do you mean actually enter the BIOS and change the boot order? Isn't that what I'm effectively doing using F12 one time boot choice?

Cheers, John

 

[mickey megabyte]

maybe i'm barking up the wrong tree, and it all depends on your particular bios, or i've misunderstood your post, but when i want to boot from a usb stick i have to go into my hard disk proirity settings, then move my usb stick up the list:




in the second screenshot, ocz-vertex is my ssd boot drive, samsung is my big spinner, and sandisk cruzer is a usb thumbdrive.

i don't have an F12 option on this machine, so that's what i have to do - as i say, ymmv...

 

[johnwillyums]

Thanks Mickey. I just tried that, rather than the one time boot option, and got the same result. It's a Gigabyte board and BIOS. Anyway, I don't think it will matter if I do get an infection in Windows.
If that happens I can just pop the side of the case and disconnect the Linux drive. I haven't tied this but I imagine without GRUB being present it will work. I only wanted to try the sweeper anyway, no probs at the moment.

Cheers, John

PS ymmv..?

 

[alphanumeric]

Both the Windows and the Linux install are on different HDDs so they are both active. As I say, I make the choice between which to run using F12 on the BIOS.
When I've done dual boot using more traditional methods GRUB always takes precedence. So you have to choose Windows in GRUB and then select it again in Winboot.
So I imagine that, with a boot choice set to USB, System Sweeper starts and sees GRUB as it is more powerful. As it cannot detect Windows, as you say, it doesn't do anything.
If I get any problems I could always just disconnect the Linux drive physically, I imagine this would work but I don't think I'll try it right now as everything is running smoothly.

Thanks for your input alph

OK, I thought you might be dual booting the traditional way. Best guess is that the presence of grub may still be messing it up. Hm, I wonder what would happen if you tried to run it on a MAC.