We have the "insufficient info to troubleshoot" close reason:

Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers.

But does this apply to questions where it's essentially impossible to troubleshoot the problem, no matter how much information the OP provides? This is maybe not the best example, but it's the question that made me ask:

Application does not run for domain admins

I've dealt with applications like this (FedEx and UPS, for example) and they're a nightmare to get right.

I voted to close as "Too Broad" because, as I said, I think it's usually impossible to do this remotely. But is that the best reason? Or should this type of question be closed at all?

We have the "insufficient info to troubleshoot" close reason:

Questions seeking installation, configuration or diagnostic help must include the desired end state, the specific problem or error, sufficient information about the configuration and environment to reproduce it, and attempted solutions. Questions without a clear problem statement are not useful to other readers and are unlikely to get good answers.

But does this apply to questions where it's essentially impossible to troubleshoot the problem, no matter how much information the OP provides? This is maybe not the best example, but it's the question that made me ask:

Application does not run for domain admins

I've dealt with applications like this (FedEx and UPS, for example) and they're a nightmare to get right.

I voted to close as "Too Broad" because, as I said, I think it's usually impossible to do this remotely. But is that the best reason? Or should this type of question be closed at all?