Warning!!

Warning

• Don’t run the Program Compatibility Troubleshooter on antivirus programs, firewall software, backup software, disk utilities, or on system programs that came with Windows. This might cause data loss or create a security risk.

Do you have more information to back up that statement ?

midou35000 said:

Warning

• Don’t run the Program Compatibility Troubleshooter on antivirus programs, firewall software, backup software, disk utilities, or on system programs that came with Windows. This might cause data loss or create a security risk.

Click to expand...

Too late, I've already run most of them with no problems.....my security seems to be ok per Microsoft, MalwareBytes and HitmanPro.

JohnBurns said:

midou35000 said:

Warning

• Don’t run the Program Compatibility Troubleshooter on antivirus programs, firewall software, backup software, disk utilities, or on system programs that came with Windows. This might cause data loss or create a security risk.

Click to expand...

Too late, I've already run most of them with no problems.....my security seems to be ok per Microsoft, MalwareBytes and HitmanPro.

Click to expand...

Hi,
you may had some luck but trust it is no good way to do that cause when run the troubelshooter the AV wil think that some programme is trying to acsess his files then he will try to block it and that could leave security problems and threads.

I really don't understand how you know this is a security problem. Can you please post a reference to validate this claim?

I see this has been moved to ChillOut Room - wasn't aware it was a spoof.....sorry! However, this might be rather dangerous for those of us who aren't "hip" to your humor!

Well according to google the quote is from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Not sure why you would do it in the first place though. I'm not sure why people do lots of things though to be honest.

adamf said:

Well according to google the quote is from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Not sure why you would do it in the first place though. I'm not sure why people do lots of things though to be honest.

Click to expand...

Thanks for explanation - I misread the original post - guess I don't read carefully enough. I've complied with the MS instructions - I only ran the compatibility troubleshooter on older 3rd party programs.....I now understand what the post was for. Sorry for the confusion I created! I apologize.

I got it from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Thanks - please see my apology above. Sorry!

JohnBurns said:

Thanks - please see my apology above. Sorry!

Click to expand...

Apology accepted smile

midou35000 said:

I got it from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Click to expand...

Just some friendly advice. When posting a statement like that it is a good idea to post the link, in the initial post, where you got the information. Thanks for the information, its good to know.

Jim

Phone Man said:

midou35000 said:

I got it from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Click to expand...

Just some friendly advice. When posting a statement like that it is a good idea to post the link, in the initial post, where you got the information. Thanks for the information, its good to know.

Jim

Click to expand...

Exactly and not ignore people when they ask for it.

Windows has an elaborate system that often allows older applications to run on systems they were not designed for. Much of this involves giving the application false information about the environment in which it is running. Resorting to this trickery is hardly an ideal situation but it is often the only way to make older applications run. For most normal and otherwise well behaved applications this causes no problems and they are often able to run as designed.

The entire WOW64 subsystem on a 64 bit OS serves to provide a fake 32 environment for 32 bit applications. Much of the information the application has about it's environment is false. This trickery is necessary to allow a 32 bit application to run under the alien 64 bit environment.

But AV and system utilities are anything but normal applications. They often use device drivers or other kernel level code and often bend or break the rules that govern how a well behaved application is to behave. But do so they must if they are to perform their intended purpose. To do this safely and reliably these applications must have full and accurate knowledge of the system they are running on. Invoke any trickery and the results are unpredictable. Security software may appear to be running properly but provide little or no security.

Microsoft is well aware of these issues and thus the warning.
Make older programs compatible with this version of Windows - Microsoft Windows Help

LMiller7 said:

Windows has an elaborate system that often allows older applications to run on systems they were not designed for. Much of this involves giving the application false information about the environment in which it is running. Resorting to this trickery is hardly an ideal situation but it is often the only way to make older applications run.

Click to expand...

I do think this is interesting actually. I work with a different OS generally and this approach would be impossible. but..

it is often the only way to make older applications run.

Click to expand...

Nope, don't think so. You make the MI instructions consistent and you don't have to care about the LIC/SLIC.

Was I missing something here, someone mentioned it being a spoof and then there was an apology. I asked the OP in answer to his initial post if he could back up making a statement like that and it turned out from the following posts other people found a link about it. :huh:

Joan Archer said:

Was I missing something here, someone mentioned it being a spoof and then there was an apology. I asked the OP in answer to his initial post if he could back up making a statement like that and it turned out from the following posts other people found a link about it. :huh:

Click to expand...

No Joan, he didn't bother to answer your question so I looked it up and found his quote on MS site. He could (and should) have given his source but for some reason didn't want to. Who knows why not - keeping secret information perhaps.

adamf said:

LMiller7 said:

Windows has an elaborate system that often allows older applications to run on systems they were not designed for. Much of this involves giving the application false information about the environment in which it is running. Resorting to this trickery is hardly an ideal situation but it is often the only way to make older applications run.

Click to expand...

I do think this is interesting actually. I work with a different OS generally and this approach would be impossible. but..

it is often the only way to make older applications run.

Click to expand...

Nope, don't think so. You make the MI instructions consistent and you don't have to care about the LIC/SLIC.

Click to expand...

Microsoft has many rules that developers must follow if their software is to run on future versions of the operating system. Unfortunately, developers do not always follow these rules. In some cases they make assumptions that were true in the OS the software was designed for, but is no longer true when a change is made in a newer OS. The original behavior the developer relied on was merely an implementation detail and not contractual. In many cases Microsoft specifically warns developers not do do this, but it still happens.


Windows has elaborate systems in place that often permit these faulty applications to run, even when the developers did things they were specifically warned not to. In many cases the only way to solve this problem (aside from fixing the application) is to use a compatibility feature that causes the OS to tell the application what it wants to see, even if it is not the truth. Thus my statement.

Microsoft has taken a great deal of criticism for maintaining the complex compatibility systems that are in place. It has been suggested that offending applications should be allowed to fail, thus forcing the developers to fix the problem. But Microsoft is realistic and knows full well that in many cases this will not happen. But Microsoft will get the blame when the failures happen, even though they are due to faulty applications.

LMiller7 said:

In many cases the only way to solve this problem (aside from fixing the application) is to use a compatibility feature that causes the OS to tell the application what it wants to see, even if it is not the truth.

Click to expand...

I feel a bit sorry for Microsoft actually. I write programs for IBMi. If their documented API doesn't work they fix it almost immediately. No-one tries to trick API calls (mostly you can't even if you want to) - it just doesn't happen. It is a tiny market though of course but if you found and relied on an undocumented "feature" that was removed or fixed in a later release then you would be insane if you thought the os provider would or should continue to support it.

Phone Man said:

midou35000 said:

I got it from here Make older programs compatible with this version of Windows - Microsoft Windows Help

Click to expand...

Just some friendly advice. When posting a statement like that it is a good idea to post the link, in the initial post, where you got the information. Thanks for the information, its good to know.

Jim

Click to expand...

Hi Again,
Thanks for your post and friendly advice i apreciate it and the errors i made will happen again am so sorry