Can't see Instagram in Firefox?

Trouble was, that Instagram and embedded Instagram pictures recently stopped loading in Firefox.
This also affects other Gecko-based browsers.
> If you want to skip the story, jump to solution.

While I also use NoScript on desktop Firefox, and on Firefox for Android, all the necessary instagram domains were allowed.

On the desktop, I'm mostly using Firefox 39.0.3, because it plays well with Flash. (There were no issues like that with other browsers.) First I thought, that this was because I wasn't using the latest Firefox. As this Firefox version plays well with Flash, I didn't want to upgrade to the latest version, because with the latest Firefox, Flash playback on YouTube is jerky since Firefox 40.

But the Instagram issue repeated, when I was also using the latest Firefox for Android. Initially I thought, that this was the fault of Instagram, and since I don't use Instagram or Facebook, I didn't think much beyond that. And for a month or so, I couln't resolve it.

But when Instagram showed in a different computer in the latest desktop Firefox (43.0.4) with the same extensions installed, I began to investigate again.

When reloading a random Instagram page while also watching the Firefox Browser Console, I found an error, which, in pasted form, looks like this:

05:16:59.308 An error occurred during a connection to instagramstatic-a.akamaihd.net:443.

Peer attempted old style (potentially vulnerable) handshake.

(Error code: ssl_error_unsafe_negotiation)
1

After some searching, I found the solution in a game forum.

SSL safe negotiation setting

Turned out, that when perusing the Privacy Settings extension of Firefox, I had turned all the settings to most secure, and among them turned on security.ssl.require_safe_negotiation. After I turned that off, Instagram showed again.

If you don't have the Privacy Settings extension installed, go to about:config and type in or paste security.ssl.require_safe_negotiation . The boolean setting value for it should be false. If not (if it's true), then double-click the setting or press enter on it to set it to false. Or right-click for context menu to Toggle.

Otherwise, the Privacy Settings extension is awesome, and I recommend it to everyone.

Whereas people who manage instagramstatic-a.akamaihd.net, should implement new-style SSL/TLS handshakes to keep their corner of the web safe.

So this was the issue that affected me.

NoScript

If, on the other hand, the above is not an issue, then you might be having NoScript installed to defend your browser from malware, and among other things, it's blocking Instagram domains, which means they're not in the whitelist. Jump to domains.

NoScript has a blue "S" button that shows the status of whether a page is completely blocked, half-blocked (content from other domains has been blocked, which is most common), or completely allowed.

That button is usually visible in the location bar, or accessible through Firefox's hamburger menu. (If the blue 'S' is not there either, click the green Customize button in the hamburger menu to see if the NoScript button is listed in the 'Additional Tools and Features' section.)

One can change NoScript domain permissions thus:
* Hover the pointer over the blue "S" button, which launches a menu with a list of domains. If the NoScript menu is very long, it has small up and down arrows for scrolling.
* To whitelist a domain, click on "Allow domainname.tld". Alternately, domains can be blocked by clicking on "Block domainname.tld". This can be done in one go for several domains.
* Once the cursor hovers away from the menu, NoScript will automatically reload the affected page (or pages in other tabs). If a page or pages don't reload (per custom settings), they can be reloaded manually.

For Instagram, the following domain names must be allowed:

platform.instagram.com
instagramstatic-a.akamaihd.net
www.instagram.com

The above are all third-level domains, because they contain three name components separated by periods/dots.

By default, NoScript shows only base second-level domains, such as instagram.com without the www and a dot. For most common users with NoScript, allowing instagram.com and akamaihd.net is sufficient.

Independence Day: Resurgence website and Firefox

A quick post: www.warof1996.com might not display in Firefox and other Gecko-based browsers.

The reason is that the site is based on WebGL, and Firefox blocks WebGL, if the GPU (video card) driver is out of date or does not support WebGL.

The solution in Windows is to update GPU drivers either through the computer manufacturer's website or through the site of the GPU supplier — one of Intel, nVidia, or AMD/ATI, but not limited to only these.

Thorough care should be taken to match the driver to the correct display adapter model.

If that doesn't work, the GPU is too old, or EOL'd.

I strongly recommend not to force Firefox to use WebGL, because this move can damage hardware.

The alternative is to use Google Chrome or Chromium, which probably uses a CPU-based workaround; but if either the graphics adapter or the CPU or both are too old, then rendering is unlikely to work, or is too slow.

> Explanation — contains minimum driver versions that support WebGL.

In addition, visit about:support in Firefox and the Graphics section therein, which also recommends the minimum driver version for WebGL (Direct2D, etc). The posting contains the same warnings about possible damage to hardware if Firefox were forced to use WebGL.

System requirements

This table is incomplete. I've only gotten to test the website on three computers (with some reservations), and gotten an external report about another.

PC	Hardware/software specifications
	CPU	GPU	RAM	OS	Fx	Chrome	Notes
ASUS K53SC notebook	Intel Core i3 2310M @ 2.1 GHz, dual-core	i:Intel HD Graphics 3000 d:nVidia GeForce GT 520MX	4 Gb DDR3, 665.1 MHz	Windows 7 SP1	Yes	Yes	Required driver updates: I had to upgrade both Intel and nVidia drivers through downloading them from their respective websites.
ASUS U46SV	Intel Core i5 2410M @ 2.3 GHz, dual-core	i: Intel HD Graphics 3000	8 Gb	Windows 10 (build unknown)	Slow	Not tested	Website opens, but performance is slow and jerky, and the fan began working intensely.
	d:	nVidia GeForce GT 540M
ThinkPad R60e (0657-3WG)	Intel Core Duo T2400 (Centrino)	Mobile Intel 945GM Express	2 Gb DDR2 (an upgrade from just 512 Mb)	Windows XP SP3	No	Slow / ok	Rendering was slow, but the site was usable. Chrome: 48.0.2564.109 32-bit; Blink 537.36 JavaScript: V8 4.8.271.19, (This version already announced that it's to be retired on Windows xp.) Instead of OpenGL, Chrome's default renderer in Windows is ANGLE, which translates OpenGL ES to Direct3D, as it has better driver support. Thus, results for Chrome can differ.
hp dv5204ea notebook	Intel Celeron M 410 @ 1.46 GHz	Mobile Intel 945GM Express	1 Gb DDR2, 266 MHz	Windows XP SP3	No	Too slow	While I did upgrade the driver, its version is still less than required: The latest Windows XP driver for this GPU is 6.14.10.4926 (15.02.2008), but Firefox wants at least version "6.1400.1000.5218".
PC	CPU	GPU	RAM	OS	Fx	Chrome

All this does not yet indicate much as to what the titular website's actual system requirements are. In notebook computers, the default video card used by any program in Windows is the integrated adapter, while nVidia software provides an option to launch programs using its own GPU.

The Asus notebook with greater specifications falls below the threshold, whereas the Asus notebook with slightly lesser specs, an older operating system and updated video drivers shows the website nicely.

Windows Update not working, error 0x8DDD0018

This can happen with Windows XP (Service Pack 3), but may not be ruled out for Vista and 7.

Windows Update error 0x8DDD0018, by which the Microsoft Update website now very helpfully explains that one or more of these services are not running:
* Automatic Updates
* Background Intelligent Transfer Service (BITS);
* Event Log

Even if all these services are running, and Windows Update refuses to run, then the culprit is the Windows Installer service not being active.

Run services.msc and then start Windows Installer. Refresh the Windows Update website. #worksforme

Manipulating page styles with the new Greasemonkey

This article assumes that the reader knows some JavaScript and a fair share of CSS, and how to create userscripts for Greasemonkey.

The argument for using Greasemnkey is that it allows for a more straightforward implementation of user-created styles, which don't require remote storage, such as userscripts.org.

Well, as of recently, it became impossible to manipulate styles on pages with modern versions of Greasemonkey running within Firefox and SeaMonkey.

I suppose this might have happened during the transition from Firefox 12 to some newer version. Oddly, the version of SeaMonkey has always remained the same, so this should somehow have ruled out that issue. Then I began thinking of NoScript — which is about the only extension maintained well for both SeaMonkey and Firefox, and updatd accordingly — but I'm not going to point any fingers, just because I don't know what the real cause is.

So, the situation happened to me using SeaMonkey 2.5 (which I am not using often, though planning to upgrade one day) with Greasemonkey 0.9.13.1, and in Firefox 15 with about the latest modern releases of Greasemonkey (0.9.22—1.x).

Greasemonkey is officially available only for Firefox, but since SeaMonkey 2.x is not supported by many extension developers, then Philip Chee decided to modify ostensibly free software extensions originally made for Firefox to then post them at xsidebar.mozdev.org for other SeaMonkey users. Some of the extensions are modified by request of other users. So the most recent Greasemonkey version for SeaMonkey 2.3 or newer is 0.9.13.1, which is modern, but by no means the newest fare.

If you think usescripts somehow stopped working, then this is not quite so. Compared to older implementations, Greasemonkey has just evolved and so have ways to manipulate styles with usescripts. IMHO.

The traditional, or classic, way of inserting lines of style code in a Greasemonkey userscript was something like this:

document.styleSheets[0].insertRule('DIV[class=pagecontent] {width:auto !important; max-width:1014px !important;}', 0);

^ Nevermind !important, which was meant to override existing online style rules. Writing declarations with [square brackets] is also clunkier, but more reliable.

Now, there are a few things about the metadata block to remember when composing a userscript: @namespace and @grant.

• @namespace does require that something is written for it. For the example I had, I wrote random, and it works for a test script, but the string can't be empty and has to be meaningful, per instructions given in the link.
• With the second, I set @grant to none.
  T., 29.01.2013. update:
  @grant is a new(ish) security measure to limit API access of a script. With this it's possible to grant none (no API access) and grant GM_*, where script lines starting with GM_* are allowed. One such example is the simplified way of modifying CSS styles through GM_addStyle. To allow GM_addStyle, set

  @grant GM_addStyle

  In conclusion, this is what I think is something that I overlooked when initially writing the blog post herein.

Interestingly, I discovered that @include strings can be equipped with wildcards. This could be an age-old feature, but this saved me a bit of effort in writing userscript code:

// @include       *.wikipedia.org/wiki/*

• By not including http:// and https:// protocols, the userscript should work for domains under both;
• The asterisk * before the primary domain (separated by a dot) allows for inclusion of subdomains. Anyhoo, the new way to insert custom style blocks is this:

GM_addStyle("DIV.pagecontent {width:auto !important; max-width:1014px !important;}")

Works for me.

Somehow installing, configuring, and using NoScript in K-Meleon 1.5 via Wine

I am assuming that you probably already know how to use Wine and know your way around the computer.

The conditions: Knoppix 4.0.2, because it runs passably with 128 Mb of RAM, in a situation where no swap space is available. This version of Knoppix has a really outdated version of Wine, which makes it difficult to use Windows programs there. There may be people stuck with either that version of Knoppix or that old version of Wine. At least this post provides a case study, which I hope could be of some interest.

The only reasonable place I could find NoScript for K-Meleon 1.5.4 is from extensions.geckozone.org/KMES-NoScriptEn. The version is 1.7.8.0 and it's from 17.06.2008 (that's 2 and 3/4 years old as of April 2011).

First off, change installer's .exe file rights for it to be an executable. Like this from the command line:

chmod u+x "K-Ext(1.1-1.5-1.6)_NoScript(1.7.8.0).exe"
^ u = for current user; + = add/enable; x = executing;
The filename is wrapped in double quotes, because it contains parentheses "()".

In my case, the first round of installation didn't work. Later I specified this target install directory:

z:\mnt\hda1\Program Files\K-Meleon
^ can't remember if I specified an upper- or lowercase letter z

and installation worked after that.

K-Meleon should not be running during installation, so run it after installation.

27.04.2011.–: After a relatively quick-and-dirty article which turned out to be far more specific than originally anticipated and still quick-and-dirty, I've updated the following with information which will make K-Meleon slightly easier to use as it is, with what the setup is and all...

When running K-Meleon through Wine in Knoppix 4.0.2 (remember that it's from 2005 and very outdated) and when you're stuck with such a set-up:

• The NoScript button menu can be used with a mouse by right-clicking on the NoScript button and holding the pointer device button down and dragging the cursor to the necessary command (shortcut menus will otherwise turn off after right-clicking on an item and hovering a mouse cursor over its menu; I've seen this in TWM, don't know how it works in other window managers).
  Other ways:
  • Click on the NoScript button, then use menu hotkeys (underlined) to perform a function;
  • or consider dragging the pointer through the NoScript menu via the main Tools menu.
• Saving configuration changes in the NoScript Options window does not work, because it's impossible to save settings by clicking the OK button, but you can otherwise close the window (saving options may work with newer versions of Wine; haven't tried this myself).
  Workarounds:
  
  • Configuring NoScript is possible only at about:config for settings (use the noscript text pattern in the about:config search bar to get NoScript-specific settings);
  • ^ Consider removing some default domains there from the noscript.default string;
• Worse, the NoScript menu in K-Meleon (at least in the given configuration and set-up) won't show domain names in its menu (Shock! Horror!).
  • Now, the whitelist, which is not shown in about:blank, is only configurable in prefs.js at the local K-Meleon profile folder on the hard drive (from where K-Meleon is run). If you don't know what the prefs.js location of the current profile is, open Preferences, go to "Privacy & Security" preference category, click on the Cache tab and see the "Cache Folder:" entry, which shows the location of the current profile folder.
    An example location is here:
    

    "/mnt/hda1/Program Files/K-Meleon/Profiles/g1bb3r1sh.default"

    So, edit the prefs.js file with a text editor at this line:
     
    user_pref("capability.policy.maonoscript.sites","place.doma.in nam.es here.com in.alphabetic.al ord.er.com ea.ch doma.in na.me separated.wi.th a.space.com and.do not.break.the.li.ne");
     
    Make sure just in case that K-Meleon is not running when editing the file, because if you've saved the file and then exit K-Meleon, then K-Meleon is highly likely to overwrite your changes.
    13.09.2011.

    Given that I had been using K-Meleon like that for a longer while, I created a menu item in the TWM window manager, where I could directly open the prefs.js file from the menu.
  • Alternately, adding sites to whitelists works from the menu (see above), but since the above configuration does not make it possible for the K-Meleon URL bar to function and display addresses, then a user is limited to knowing the site domain and web page address in the following ways:
  • In K-Meleon, the tab bar is typically shown by default, so it should be enough to hover the mouse cursor over a page's tab button: This displays the tool tip, which then shows the site/page title and its partial address.
  • A user might know the site's domain name, if they've entered it themselves (because of limitations, entering a URL goes through editing bookmarks and accessing a bookmark set up for just that).
    A user can specify that only top-level domain names are added, by setting this in NoScript preferences through about:config, only that the whole point of NoScript to me is the fine-grained way in which some subdomains can be whitelisted, so that disruptive ones are duly excluded. Unfortunately, not directly seeing a site's domain name in the URL bar has security implications, including the fact that the non-functioning URL bar doesn't change color when visiting a secure site, though a bottom-right status bar indicator should work. Preferably, only safe sites should be visited. (Avoid clicking e-mail links, if you know they're dubious, but this requires at least some user education and this is where NoScript is useful. There is nevertheless a greater amount of security in running K-Meleon equipped with NoScript, no matter how limited it is, through Wine in Linux than in Windows 9x);
  • Some necessary domain names pulled by a page from (a) differently-named domain/s to fetch scripts and/or stylesheets across sites and subdomains are not displayed anyway (not even in the NoScript menu), so there is no direct way of learning which other domains must be allowed for scripting.
  • Consider disabling NoScript for the duration of the session, if you're using a service which requires logging in and if it's been impossible to learn what are the exact outside domains with necessary scripts.
  • The third option is to import domain names from other NoScript settings in other prefs.js files. This actually works. But what if using a new service that users a non-primary domain name for scripting? Or what if an existing service sometimes changes its subdomains?

What's left of sidebars for Netscape

Ed Mullen has a great page on Netscape and Mozilla tips and even a page that includes installable links to sidebars that can still be added to SeaMonkey 1.1.xx, a successor to Netscape 7/8 and Mozilla Application Suite.

Unfortunately, some of the sidebars are now outdated, half-work, redirect, cannot be found anymore or are completely offline.

Below is a selection of sidebars I found to be interesting to check them out.

Sidebars that still work:

• The Google sidebar works! Yay!
• The Real.com Guide sidebar only offers search for audio, video, and radio stations (no actual Guide to speak of).

...That are outdated:

The CNN Expanded Sidebar is still live, but stopped having updates since two years ago on March 2, 2009: The Dow Jones index dropped below 7000 on that day, because AIG had a record loss, tech gadgets had become a luxury, and "Twilight" stars were huge.

The links to news sites don't work, because they use a redirect via info.netscape.com (which now redirects to netscape.aol.com ).

In terms of context, the "Last updated" text in the sidebar is inaccurate, because it's most likely a script. That sidebar page is now a virtual time capsule of World news.

Netscape Sidebars

...that redirect:

• Netscape WebCenter Travel (webcenter.travel.netscape.com) — Ah, well, this at least redirects to travel.aol.com, but that's it. At least it's topical.
• Netscape Celebrities (celebrities.netscape.com) — redirects within the sidebar to netscape.aol.com.
• Netscape TV Listings (tv.netscape.com) — redirects in-sidebar to netscape.aol.com.

...that don't work anymore:

(in descending order of importance)

• Netscape Time Zone Converter (cgi.netscape.com) — "Not found" — Ed Mullen's screenshot of it is now a historical artifact;
• Netscape Netbusiness — because netbusiness.netscape.com is completely offline (no 404 page, even);
• Netscape Netbusiness Industry Headlines (netbusiness.netscape.com) — domain is offline;
• Netscape Netbusiness Search (netbusiness.netscape.com) — offline;
• Netscape DevEdge (developer.netscape.com): "This tab is not available right now." — Taken offline since about 11.10.2004 and then moved to devedge-temp.mozilla.org/index_en.html
   
• Netscape Home Improvement (homeimprovement.netscape.com) — "Not Found";
• Netscape Home Improvement House and Home (homeimprovement.netscape.com) — "Not Found";
• Netscape Lifestyles Pet tools (lifestyles.netscape.com) — "Not Found".
   
• American Greetings (lifestyles.netscape.com) — "Not Found"

• The OS/2 sidebar does not work either, because os2.org cannot be reached.

Speaking of which — OS/2 has officially outlived Windows 9x, because according to screenshots, Mozilla Firefox 3.5.4 works in it. OS/2 can also run OpenOffice.org 3.1.1 and OS/2 now lives on as eComStation, where Firefox 3.6 and 4.0 (beta) can also be run.

eComStation is capable of running OpenOffice.org 3.2, VLC Media Player 1.1.4, and CUPS, a free software printer framework (modern printer support).

While Windows 9x only supports Mozilla Firefox 2.0, OpenOffice.org 2.4, and has ageing support for printers (I admit as much that some printers useless with CUPS are supported in Windows 9x)...

msn connectivity of Pidgin 2.6.6 in Windows 98

I very recently attempted to connect with Pidgin IM 2.6.6 (the last to run on Windows 98, AFAIK) to the .NET Messenger Service, which handles Windows Live Messenger connections. In short, I wanted to connect to msn, but it was impossible because of certificate issues.

The typical solution is to upgrade Pidgin to version 2.7.6, but this version relies on the gtk+ 2.10.xx or newer runtime (a library), which won't run on Windows 98/SE, so users of this operating system may feel stuck.

The solution is thus:

• Close Pidgin.
• The real solution is at SQuID's rants blog post or at the Pidgin developer site.
• Caveats: The filenames must be
  Microsoft_Secure_Server_Authority_2010.pem
  and
  Microsoft_Secure_Server_Authority_2010.pem
  If by any chance the files saved save as *.pem.log
  or anything that does not directly end with a .pem extension, then rename them to *.pem (the asterisk stands for filenames).

The following was my initial solution, but there was a chance that it might not have worked. For other purposes, I left it as a tutorial on how to export and save certificates in W98/Me.

• Go to
  C:\WINDOWS\Application Data\.purple\certificates\x509\tls_peers
  or
  C:\WINDOWS\Profiles\Profilename\Application Data\.purple\certificates\x509\tls_peers
• There you will see what appear to be .com (command) files which are appropriately shown as such by Windows Explorer, but they are actually certificates. Amongst them you will see the omega.contacts.msn.com file. Back that file up by moving it somewhere else, but keep that directory window open and copy its address bar contents into the clipboard.
• With Internet Explorer, connect to
  https://omega.contacts.msn.com
  You may get a denied directory listing, but perhaps the most important part of it is that you'll be presented with a new certificate. —
• View the certificate, go to the Details tab.
• In the Details tab, click the "Copy to File..." button;
• In the Certificate Manager Export Wizard, click next;
• Choose the Base64 encoded X.509 (.CER) format, click the Next button;
• In the Export File Name step, browse to
  C:\WINDOWS\Application Data\.purple\certificates\x509\tls_peers
  or your profile location (best now to paste the location of .purple certificates into the File Name field and then pressing the Enter button for the filepicker to reach the folder), then write the filename as omega.contacts.msn.com, click Save. As the full filename path is now given in the "File name:" field, click Next.
• In the next step, you'll see the certificate export summary, where you'll just have to click Finish and the system will prompt that the export has completed successfully. But that's not everything.
• Restore the abovementioned tls_peers folder window and you'll see that omega.contacts.msn.com may not be that, but omega.contacts.msn.com.cer

  (that is, if you can see the .cer extension. If not, but the file has a certificate icon and not a program icon, go to View > Folder Options > View tab > and in Advanced Settings, uncheck "Hide file extensions for known file types", click OK).

  The solution is to rename the .cer file by removing .cer from the filename. Windows will ask for a confirmation as to changing the file extension (the renamed file will have .com extension). Confirm the rename.
• If it's impossible to change Windows settings as to showing filename extensions (you may be using a work computer, but such a situation is rare with a Windows 9x PC), and if you still can access MS-DOS Prompt, then rename the file from there:
  Type
  cd "C:\WINDOWS\Application Data\.purple\certificates\x509\tls_peers"
  or just type
  cd "
  and paste the certificate directory address by accessing the window menu (click once on the MS-DOS icon and choose Paste from the Edit submenu), type another quote,
  press Enter.
  Your profile directory path may vary as stated above depending on settings.
  Use dir command to get a directory listing. That should show short and long file names. If you see omega.contacts.msn.com.cer as the filename of the msn certificate, rename it:
  rename omega.contacts.msn.com.cer omega.contacts.msn.com
  That should do it. Type exit, press Enter key to close the MS-DOS Prompt window.
• Now start Pidgin and see what happens at the msn login. I could successfuly log in, so you should hopefully not have any trouble either.

I got the initial above solution from Ticket #12906 at the Pidgin developer site.

Ctrl+V, Ctrl+C, Ctrl+X disabled, but Shift+Del/Ins & Ctrl+F not?

As the title suggests, it was one day impossible to cut, copy and paste in Windows XP across apps using Ctrl+X, Ctrl+C, Ctrl+V and to use left-Ctrl+PgUp/PgDn to move around tabs in SeaMonkey. Shift+Del, Ctrl+Ins and Shift+Ins worked, so did Ctrl+F, Ctrl+Q and a few other keyboard shortcuts.

The keyboard was Logitech Internet Pro Keyboard (iTouch Pro or somesuch).

I did do my standard run through tech forums (even a keyboard driver change) and scans with software (Spybot Search & Destroy didn't find anything). MBAM found a few things, I deleted them (the scan log of this well below).

LATER it turned out that the non-standard www button on the keyboard was STUCK. I had it moved to normal position and then using the Ctrl+... keys worked like a charm, even after a restart. Trouble was that I failed to test if the Ctrl+ keys also worked after the MBAM scan and correction.

* Some text is in Estonian.

---

Malwarebytes' Anti-Malware 1.46
www.malwarebytes.org

Andmebaasi versioon: 4387

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

4.08.2010 10:19:46
mbam-log-2010-08-04 (10-19-46).txt

Kontrolli tüüp: Kiirkontroll
Kontrollitud objekte: 180205
Kulunud aeg: 9 minut(id), 31 sekund(id)

Nakatunud mälu objekte: 0
Nakatunud mälu mooduleid: 0
Nakatunud registrivõtmeid: 1
Nakatunud registri väärtusi: 1
Nakatunud registriandmeid: 0
Nakatunud kaustu: 2
Nakatunud faile: 0

Nakatunud mälu objekte:
(Pahavara ei tuvastatud)

Nakatunud mälu mooduleid:
(Pahavara ei tuvastatud)

Nakatunud registrivõtmeid:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{faad2038-c371-473d-86f1-5b11d39c3775} (Rogue.Multiple) -> Quarantined and deleted successfully.

Nakatunud registri väärtusi:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Network\uid (Malware.Trace) -> Quarantined and deleted successfully.

Nakatunud registriandmeid:
(Pahavara ei tuvastatud)

Nakatunud kaustu:
C:\Documents and Settings\All Users\Application Data\SalesMonitor (Rogue.Multiple) -> Quarantined and deleted successfully.
C:\Documents and Settings\All Users\Application Data\SalesMonitor\Data (Rogue.Multiple) -> Quarantined and deleted successfully.

Nakatunud faile:
(Pahavara ei tuvastatud)