Windows XP Pro 64-bit: Unable to connect the serivce?

[Collector]

Hi I cannot get malwarebytes antimalware working on windows XP 64-bit since the last 3.6 update gave me a no proc error, I downgraded 3.5 as that was the reported last supported version for XP and this is the error I get....

 

Support tool doesn't work because of this error:

And doesn't specify which update it needs to work, I have already tried install all three: 4.0.1, 4.0.2 and 4.0.3 and none seem to fix this error....

 

Please help, thanks!

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

1. Download Malwarebytes Support Tool
2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
3. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
4. Place a checkmark next to Accept License Agreement and click Next
5. You will be presented with a page stating, "Get Started!"
6. Click the Advanced tab
   
    
7. Click the Gather Logs button
   
    
8. A progress bar will appear and the program will proceed with getting logs from your computer
   
    
9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
   
    
10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
       

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

Spoiler

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

[Collector]

oh can't edit post to fix up my grammar errors......

 

gg no re...

 

5 minutes ago, Malwarebytes said:

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

  Reveal hidden contents

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

1. Download Malwarebytes Support Tool
2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
3. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
4. Place a checkmark next to Accept License Agreement and click Next
5. You will be presented with a page stating, "Get Started!"
6. Click the Advanced tab
   
    
7. Click the Gather Logs button
   
    
8. A progress bar will appear and the program will proceed with getting logs from your computer
   
    
9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
   
    
10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
       

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

  Reveal hidden contents

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

  Reveal hidden contents

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

Yes did you not read my post? Oh you're a bot, nevermind....

 

[plb4333]

22 minutes ago, Collector said:

Hi I cannot get malwarebytes antimalware working on windows XP 64-bit since the last 3.6 update gave me a no proc error, I downgraded 3.5 as that was the reported last supported version for XP and this is the error I get....

 

Support tool doesn't work because of this error:

And doesn't specify which update it needs to work, I have already tried install all three: 4.0.1, 4.0.2 and 4.0.3 and none seem to fix this error....

 

Please help, thanks!

Have you tried NET 4.5? or even 4.7.2 it's the highest one

[plb4333]

I just seen where WinXP doesn't allow for NET 4.5 and higher, sorry about that. It might be MBAM has to use 4.5 and higher since WinXP is getting phased out, not sure

 

[plb4333]

3 minutes ago, plb4333 said:

I just seen where WinXP doesn't allow for NET 4.5 and higher, sorry about that. It might be MBAM has to use 4.5 and higher since WinXP is getting phased out, not sure

 

You might want to make sure your NET framework installations are ok with this Microsoft tool to diagnose and fix .NET framework installs

https://download.microsoft.com/download/2/B/D/2BDE5459-2225-48B8-830C-AE19CAF038F1/NetFxRepairTool.exe

 

[Firefox]

Hello and Welcome...

Let me start by saying first that XP 64bit I believe is not really supported, but lets see if you can at least get us the logs below to start somewhere.

Let's try and get some logs first so the team can review them and see if they can tell what may be causing your issues....
 

1. FIRST: Create and obtain Farbar Recovery Scan Tool (FRST) logs
2. Download FRST and save it to your desktop
   Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
3. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
4. Press the "Scan" button
5. This will produce two files in the same location (directory) as FRST: FRST.txt and Addition.txt
   
   • Leave the log files in the current location, they will be automatically collected by mb-check once you complete the next set of instructions
     
6. NEXT: Create and obtain an mb-check log
7. Download MB-Check and save to your desktop
8. Double-click to run MB-Check and within a few second the command window will open, press "Enter" to accept the EULA then click "OK"
9. This will produce one log file on your desktop: mb-check-results.zip
   
   • This file will include the FRST logs generated from the previous set of instructions
   • Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area
     
   
   
   

 

[dcollins]

Windows XP 64-bit is not supported. You can view this on our product page: https://www.malwarebytes.com/premium/#tech-specs

[Collector]

18 hours ago, plb4333 said:

You might want to make sure your NET framework installations are ok with this Microsoft tool to diagnose and fix .NET framework installs

https://download.microsoft.com/download/2/B/D/2BDE5459-2225-48B8-830C-AE19CAF038F1/NetFxRepairTool.exe

 

No the later versions of .NET framework indeed doesn't install on windows xp machines....so if the support tool requires 4.5 or newer I can't run it on XP then.....

 

I have tried that and apparently it failed to repair the installations citing these log files:

C:\WINDOWS\windowsupdate.log

C:\DOCUME~1\Z\LOCALS~1\Temp\FixDotNet.log

C:\DOCUME~1\Z\LOCALS~1\Temp\NetFxSetupEvents.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_depcheck_NETFX_EXP_35.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_dotnetfx35error.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_dotnetfx35install.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_dotNetFx40_Client_x86_x64_decompression_log.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_dotNetFx40_Full_x86_x64_decompression_log.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_NetFxRepairTool_decompression_log.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_SetupUtility.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistMSI3D81.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistMSI3F2E.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistMSI40FE.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistMSI4904.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistUI3D81.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistUI3F2E.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistUI40FE.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredistUI4904.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_051248_765.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_051248_984.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_052208_000.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_052208_250.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_052424_703.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_052424_968.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_085128_640.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_wcf_CA_smci_20181105_085128_875.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_BITS.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_amd64_20171025151327.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_amd64_20171025151327_000_vcRuntimeMinimum_x64.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_amd64_20171025151327_001_vcRuntimeAdditional_x64.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_x86_20171025151323.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_x86_20171025151323_000_vcRuntimeMinimum_x86.log

C:\DOCUME~1\Z\LOCALS~1\Temp\dd_vcredist_x86_20171025151323_001_vcRuntimeAdditional_x86.log

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework 4 Setup_20181105_164936609-MSI_netfx_Core_x64.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework 4 Setup_20181105_164936609-MSI_netfx_Extended_x64.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework 4 Setup_20181107_105058906-MSI_netfx_Core_x64.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181029_104622828-MSI_vc_red.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181029_105650343-MSI_vc_red.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181105_165247515-MSI_vc_red.msi.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework 4 Setup_20181105_164936609.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework 4 Setup_20181107_105058906.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework Repair Tool Legacy_20181107_105056765.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft .NET Framework Repair Tool_20181107_103912609.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181029_104622828.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181029_105650343.html

C:\DOCUME~1\Z\LOCALS~1\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20181105_165247515.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2478063_20181105_131127250-Microsoft .NET Framework 4 Client Profile-MSP0.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2478063_20181105_131127250-Microsoft .NET Framework 4 Extended-MSP1.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2544514_20181105_132037656-Microsoft .NET Framework 4 Client Profile-MSP0.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2544514_20181105_132037656-Microsoft .NET Framework 4 Extended-MSP1.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2600211_20181105_132242468-Microsoft .NET Framework 4 Client Profile-MSP0.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2600211_20181105_132242468-Microsoft .NET Framework 4 Extended-MSP1.txt

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2478063_20181105_131127250.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2544514_20181105_132037656.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2600211_20181105_132242468.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2478063_20181105_131127250.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2544514_20181105_132037656.html

C:\DOCUME~1\Z\LOCALS~1\Temp\KB2600211_20181105_132242468.html

C:\DOCUME~1\Z\LOCALS~1\Temp\FixDotNet_HKCR_Installer.regdump

C:\DOCUME~1\Z\LOCALS~1\Temp\FixDotNet_HKLM_Installer.regdump

 

12 hours ago, Firefox said:

Hello and Welcome...

Let me start by saying first that XP 64bit I believe is not really supported, but lets see if you can at least get us the logs below to start somewhere.

Let's try and get some logs first so the team can review them and see if they can tell what may be causing your issues....
 

1. FIRST: Create and obtain Farbar Recovery Scan Tool (FRST) logs
2. Download FRST and save it to your desktop
   Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
3. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
4. Press the "Scan" button
5. This will produce two files in the same location (directory) as FRST: FRST.txt and Addition.txt
   • Leave the log files in the current location, they will be automatically collected by mb-check once you complete the next set of instructions
6. NEXT: Create and obtain an mb-check log
7. Download MB-Check and save to your desktop
8. Double-click to run MB-Check and within a few second the command window will open, press "Enter" to accept the EULA then click "OK"
9. This will produce one log file on your desktop: mb-check-results.zip
   • This file will include the FRST logs generated from the previous set of instructions
   • Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area
   
    

 

 

Hmmm, apparently kaspersky things the certificate bleeping computer uses is invalid....

 

The MB-Check program downloads fine without issue....

Logs attached...

10 hours ago, dcollins said:

Windows XP 64-bit is not supported. You can view this on our product page: https://www.malwarebytes.com/premium/#tech-specs

Oh well it was working fine with the previous installments...until malwarebytes decided to ask for an update and I said yes and now it doesn't work.....the program didn't even bother to check for compatibility issues or if there would be a chance of it not working and telling me this before I update.....

mb-check-results.zip

[exile360]

Yes, unfortunately that's likely due to the fact that XP Pro x64 isn't a supported platform so the QA team didn't test with it and the Dev team didn't code for it (or code in any special compatibility checking/notification routines).  That said, it should still be possible to reinstall the older version if you wish.  Just go to a site such as filehippo.com and download any of the available versions there to test and see if they work on your platform, just keep in mind that as the version you use becomes more outdated the signatures in use in its databases will increasingly be replaced by newer ones that can only be read and used by the engines in more current releases, so it won't be as secure as those newer versions would be (this also doesn't account for other enhancements and new features and capabilities outside of the database/core malware detection engine such as the other protection components).

It isn't an ideal solution, but should at least allow you to get it up and running for now until you can find a better solution or until you migrate to a more current operating system (a good idea anyway if possible considering XP x64 met end of life several years ago and XP in general is also at end of life at this point meaning no more patches or security updates from Microsoft will be created for it).

You can disable the option for Malwarebytes to check for/download new versions of the software under Settings>Application.  Just disable the two options there so that you aren't offered any updates/upgrades for newer builds and you should then be able to stay on the last working version for your platform.

[dcollins]

The Support Tool doesn't require .Net 4.5, it should work on XP, however it's also not compatible with XP 64-bit.

And to clarify, "not supported" doesn't mean it won't work. "not supported" means we don't test against that operating system, so it may work (as you saw before) or it may not (as you're seeing now). Since it was working before, the best thing I can recommend is to download and run mb-clean, then install the latest 3.5 version, which can be downloaded from https://downloads.malwarebytes.com/file/mb3_legacy. 

[Collector]

On 11/7/2018 at 12:33 PM, exile360 said:

It isn't an ideal solution, but should at least allow you to get it up and running for now until you can find a better solution or until you migrate to a more current operating system (a good idea anyway if possible considering XP x64 met end of life several years ago and XP in general is also at end of life at this point meaning no more patches or security updates from Microsoft will be created for it).

Well Microsoft did release a patch for that wannacry ransomware hole......doesn't that count?

 

On 11/7/2018 at 12:33 PM, exile360 said:

You can disable the option for Malwarebytes to check for/download new versions of the software under Settings>Application.  Just disable the two options there so that you aren't offered any updates/upgrades for newer builds and you should then be able to stay on the last working version for your platform.

Thanks...will do...

 

On 11/7/2018 at 11:43 PM, dcollins said:

The Support Tool doesn't require .Net 4.5, it should work on XP, however it's also not compatible with XP 64-bit.

Oh so then it doesn't work then? Lovely....

 

On 11/7/2018 at 11:43 PM, dcollins said:

And to clarify, "not supported" doesn't mean it won't work. "not supported" means we don't test against that operating system, so it may work (as you saw before) or it may not (as you're seeing now). Since it was working before, the best thing I can recommend is to download and run mb-clean, then install the latest 3.5 version, which can be downloaded from https://downloads.malwarebytes.com/file/mb3_legacy. 

MB-Clean failed with error:

 

mb-clean-results.txt

[dcollins]

It looks like the majority of mb-clean worked, that tool wasn't written for x64 XP either but I was hoping it might help out. I would recommend rebooting and attempting to install 3.5.1 again (https://downloads.malwarebytes.com/file/mb3_legacy) 

[exile360]

2 hours ago, Collector said:

Well Microsoft did release a patch for that wannacry ransomware hole......doesn't that count?

Not really.  Microsoft only released that patch as an emergency measure due to the number of systems infected by it.  There are far more glaring and easier to exploit vulnerabilities in that operating system which remain unpatched, and Microsoft is unlikely to patch any of those going forward.

It is obviously your decision, however I'm just telling you how it is.  Microsoft has abandoned XP (and Vista), and being a diehard Windows 7 user myself, I feel your pain.  In a few years 7 will meet its end of life, and unless things change dramatically in the future with regards to how Microsoft does things and how they treat their desktop OS customers in their latest operating systems, I will NOT be making the move to Windows 10 (or any other future version of the OS, assuming they ever do another major release beyond 10).

I'm really not trying to alarm you needlessly.  You can take a look for yourself at any of the sites that document known vulnerabilities for each OS, and you'll find a very large number impacting XP, including x64, which remain unpatched and which Microsoft probably won't be patching (many of those vulnerabilities have existed for years and have known exploits/malware in the wild which have targeted them, so MS isn't patching them even if they are being used to infect their users/customers).  As I said though, it is of course your choice.  I'm just stating this information in case you weren't ware of it, and especially if any other XP users should come across this thread who are unaware of the situations and the risks involved.

[Collector]

11 hours ago, dcollins said:

It looks like the majority of mb-clean worked, that tool wasn't written for x64 XP either but I was hoping it might help out. I would recommend rebooting and attempting to install 3.5.1 again (https://downloads.malwarebytes.com/file/mb3_legacy) 

Ah....

 

I still get the "Unable to connect the Service" error window....

 

10 hours ago, exile360 said:

Not really.  Microsoft only released that patch as an emergency measure due to the number of systems infected by it.  There are far more glaring and easier to exploit vulnerabilities in that operating system which remain unpatched, and Microsoft is unlikely to patch any of those going forward.

It is obviously your decision, however I'm just telling you how it is.  Microsoft has abandoned XP (and Vista), and being a diehard Windows 7 user myself, I feel your pain.  In a few years 7 will meet its end of life, and unless things change dramatically in the future with regards to how Microsoft does things and how they treat their desktop OS customers in their latest operating systems, I will NOT be making the move to Windows 10 (or any other future version of the OS, assuming they ever do another major release beyond 10).

I'm really not trying to alarm you needlessly.  You can take a look for yourself at any of the sites that document known vulnerabilities for each OS, and you'll find a very large number impacting XP, including x64, which remain unpatched and which Microsoft probably won't be patching (many of those vulnerabilities have existed for years and have known exploits/malware in the wild which have targeted them, so MS isn't patching them even if they are being used to infect their users/customers).  As I said though, it is of course your choice.  I'm just stating this information in case you weren't ware of it, and especially if any other XP users should come across this thread who are unaware of the situations and the risks involved.

Oh? How many more glaring exploits are there that aren't listed fixed? And have any of those been used to distribute malware?

 

It's the metro inteface right on windows 10 that you dislike to the point of boycotting them? Or is it something else? ...like those supposed preinstalled spyware...? ...especially in the free version........or so I am told....

 

But they will patch it if it infects a sizeable amount of customers, yes...? :P I read that that NSA told Microsoft specifically to NOT to patch that hole as they needed it to spy on people and then next thing they know, some random who somehow figured out the hole decided to do some actual damage....

 

Besides, doesn't malwarebytes antimalware now have zero day exploit feature? Or is that only on windows 7 and newer systems?

[exile360]

I pulled up several vulnerability/CV tracking sites and there were tons of entries for XP.  I didn't do a deep dive on it, but I have read about plenty of them in the past (major vulnerabilities being exploited by "malware X" that Microsoft isn't going to patch etc.).  I can provide some links if you'd like, but honestly you could get more relevant info from just browsing the patches MS has released for Vista/7+ since the XP extended support period expired as many/most no doubt also apply to XP as was the case more often than not in the past when all of those operating systems were still supported as there would be a version for each OS usually, including XP, so you can at least get a good idea of how many there are and how severe they may be if used to exploit the OS.

I can't speak for Microsoft and what they will or won't do; I only know that the EternalBlue/SMB vulnerability is the one and only CV they've addressed for XP since they dropped extended support for it and in the meantime, vulnerabilities remain unpatched (and sadly often in-use by the bad guys, especially in browser and plugin/extension exploits as those are the type which enable drive-by infection via malicious ads etc.).

In 8/8.1/10, it's Metro (which seems to be a regression to me), the built in adware/advertising functionality for the Microsoft store and preinstalled apps (many of which you can remove, but sadly return whenever you patch), and yes, the telemetry (this is also why I use a blacklist of specific telemetry related patches for 7 that I do not install and hide in MS Update whenever they are offered, and also have disabled and thoroughly crippled CEIP and several other functions built into the OS designed to gather telemetry).  It's also the more touch-centric interface, being a keyboard/mouse user myself.  In fact, I designed an OS shell concept that would work as an ideal hybrid for both standard keyboard and mouse navigation as well as touch, and would likely work better for touch than what they are currently doing, but of course MS has their own ideas about what is important, what works, and what people want and need.  I'd give it to them for free if they'd actually use it, but I'm certain they never would because it makes too much sense  .

As for Malwarebytes, yes, so as long as 7 continues to be supported I should be OK against the vast majority of exploits, however with XP sadly this is not the case since you're forced to use an older build for compatibility, though still, some protection is better than none that's for sure.  If/when Malwarebytes drops Windows 7 support, which could well happen, especially if the APIs in later releases of 10 change/evolve beyond the point of simple Windows 7 backwards compatibility, I'll have to reassess my decisions, though by then hopefully MS will have something new to offer that offends my sensibilities less than what they have now.

Edited November 13, 2018 by exile360

[Dleverk]

I was able to solve the problem. Good tips.
 

[Collector]

On 11/13/2018 at 10:51 AM, exile360 said:

I pulled up several vulnerability/CV tracking sites and there were tons of entries for XP.  I didn't do a deep dive on it, but I have read about plenty of them in the past (major vulnerabilities being exploited by "malware X" that Microsoft isn't going to patch etc.).  I can provide some links if you'd like, but honestly you could get more relevant info from just browsing the patches MS has released for Vista/7+ since the XP extended support period expired as many/most no doubt also apply to XP as was the case more often than not in the past when all of those operating systems were still supported as there would be a version for each OS usually, including XP, so you can at least get a good idea of how many there are and how severe they may be if used to exploit the OS.

That's a lot then since there have been quite a few updates since April 2014......

 

On 11/13/2018 at 10:51 AM, exile360 said:

I can't speak for Microsoft and what they will or won't do; I only know that the EternalBlue/SMB vulnerability is the one and only CV they've addressed for XP since they dropped extended support for it and in the meantime, vulnerabilities remain unpatched (and sadly often in-use by the bad guys, especially in browser and plugin/extension exploits as those are the type which enable drive-by infection via malicious ads etc.).

Ah I see: https://en.wikipedia.org/wiki/EternalBlue NSA warned Microsoft about it and they slowly rolled out the patch for it, then the NSA decided to be dicks just to push Microsoft further and released information on how to exploit this vulnerability and then Microsoft acted fasted and even tried to patch the old windows XP systems! Is that how the story goes?

 

So I as long as I'm not using the computer for sensitive data, minus logging in and posting on forums or other accounts that dont really hold much importance even if they got hacked, I should be good right...? Heh...😉

 

On 11/13/2018 at 10:51 AM, exile360 said:

In 8/8.1/10, it's Metro (which seems to be a regression to me)

Yeah, windows 8/8.1 was rather stable and liked it really great, but just couldn't put up with the metro UI or and flat menus....so downgraded back to windows 7 and XP......hah....

 

On 11/13/2018 at 10:51 AM, exile360 said:

the built in adware/advertising functionality for the Microsoft store and preinstalled apps (many of which you can remove, but sadly return whenever you patch)

Oh yeah the store, I like to have a clean start menu too....

 

On 11/13/2018 at 10:51 AM, exile360 said:

the telemetry (this is also why I use a blacklist of specific telemetry related patches for 7 that I do not install and hide in MS Update whenever they are offered, and also have disabled and thoroughly crippled CEIP and several other functions built into the OS designed to gather telemetry).

Are these included in the rollup monthly patches? Because I know Microsoft puts all updates into packs now in monthly updates since May or March......of this year....

 

On 11/13/2018 at 10:51 AM, exile360 said:

It's also the more touch-centric interface, being a keyboard/mouse user myself.

I have a windows phone and the metro UI is perfect here! But I agree it isn't suitable, for desktop use...... I think there were third-party programs that try to revert what windows 10 and 8 looks like down to 7 or even XP/VISTA era look.......though you need to pay as some of the good stuff are paid.....

 

On 11/13/2018 at 10:51 AM, exile360 said:

In fact, I designed an OS shell concept that would work as an ideal hybrid for both standard keyboard and mouse navigation as well as touch, and would likely work better for touch than what they are currently doing, but of course MS has their own ideas about what is important, what works, and what people want and need.  I'd give it to them for free if they'd actually use it, but I'm certain they never would because it makes too much sense  .

You did? Do you have a demo video I could see...I would like to see this supposed improved UI that just works for both touch and keyboard/mouse users that's isn't ...*ugly*.........but I guess appearance can be subjective.....

 

 

[exile360]

It wasn't the NSA that published/released them to the public, it was The Shadow Brokers group.  They published that one along with several others.

Nope, they haven't been rolled up, at least not the ones published before that time, during the era of Windows 8/8.1 and the early phase of 10 when they started pushing all their GWX (Get Windows 10) and telemetry garbage.  I can tell because those updates still show up offered separately.  This means they haven't been integrated into their monthly rollups (yet).

I don't have a video as I'm no programmer, but I did create some simple images of it and descriptive text.  I submitted it to one of the Malwarebytes Devs at one point just to get his feedback and he said it was a perfect solution for a touch/keyboard & mouse hybrid interface and I told him that's exactly what I was shooting for.  Basically the idea is that you have a series of horizontal rows, each one containing a set of icons and/or folders and they are laid out vertically in a semi-3-dimensional way where you can scroll your mousewheel or drag it with your finger to rotate it to expose more of them.  The whole thing works like a bunch of gears on a wheel and when you open a folder or program on a row, it can expand to occupy the entire row horizontally and can also expand that row to fill the screen vertically and you can manipulate it to change how much of the screen it occupies.  You can also drag the icons/folders horizontally for folders/layers that are too wide to fit onscreen all at once (similar to how you scroll horizontally on a wide image, webpage, or folder) and you have your normal START menu at the bottom of the screen, with this 3D contraption above it.  It's a 3D expansive, interactive interface that can adapt to screens of any size and layout thanks to the flexibility inherint in its design.  You can think of it like almost a 3D version of the old Windows Media Center interface, kind of similar to how the UI in the Playstation 4 works if you've ever seen that, except you have more control over the layout and how much space folders and applications occupy.  I even came up with the idea for themes for it where you could have gears on the sides or wheels or whatever to fit with the way that it moves and is laid out.

[Collector]

On 11/20/2018 at 10:48 AM, exile360 said:

It wasn't the NSA that published/released them to the public, it was The Shadow Brokers group.  They published that one along with several others.

Nope, they haven't been rolled up, at least not the ones published before that time, during the era of Windows 8/8.1 and the early phase of 10 when they started pushing all their GWX (Get Windows 10) and telemetry garbage.  I can tell because those updates still show up offered separately.  This means they haven't been integrated into their monthly rollups (yet).

ah

On 11/20/2018 at 10:48 AM, exile360 said:

I don't have a video as I'm no programmer, but I did create some simple images of it and descriptive text.  I submitted it to one of the Malwarebytes Devs at one point just to get his feedback and he said it was a perfect solution for a touch/keyboard & mouse hybrid interface and I told him that's exactly what I was shooting for.  Basically the idea is that you have a series of horizontal rows, each one containing a set of icons and/or folders and they are laid out vertically in a semi-3-dimensional way where you can scroll your mousewheel or drag it with your finger to rotate it to expose more of them.  The whole thing works like a bunch of gears on a wheel and when you open a folder or program on a row, it can expand to occupy the entire row horizontally and can also expand that row to fill the screen vertically and you can manipulate it to change how much of the screen it occupies.  You can also drag the icons/folders horizontally for folders/layers that are too wide to fit onscreen all at once (similar to how you scroll horizontally on a wide image, webpage, or folder) and you have your normal START menu at the bottom of the screen, with this 3D contraption above it.  It's a 3D expansive, interactive interface that can adapt to screens of any size and layout thanks to the flexibility inherint in its design.  You can think of it like almost a 3D version of the old Windows Media Center interface, kind of similar to how the UI in the Playstation 4 works if you've ever seen that, except you have more control over the layout and how much space folders and applications occupy.  I even came up with the idea for themes for it where you could have gears on the sides or wheels or whatever to fit with the way that it moves and is laid out.

Well I don't have a PS4 and haven't used the Media Center on windows in a while......so it's pretty hard to imagine those ideas in my head.....