Windows 10 Search
-
@Dashrender but when I want to find something, I don't want to wait for the computer to search under every damn thing under the sun to find it. I don't have time to wait for that.
The stuff in my example, it finds it instantly... I don't have to wait for my computer to search my Windows drivers folder to find a text file i'm looking for.
-
@Dashrender said in Windows: Finding Files with PowerShell:
FFS - the default search should show every damned thing under the sun then, and those buttons should only be needed to narrow things down.
But that is not what has been happening for Scott or I.
I can only hope things will get better, I already admit they are better than the Win7/8/8.1 days.
Mine changes. It lists things when I first install them, then later they stop showing up, even though they haven't been modified.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Dashrender said in Windows: Finding Files with PowerShell:
FFS - the default search should show every damned thing under the sun then, and those buttons should only be needed to narrow things down.
But that is not what has been happening for Scott or I.
I can only hope things will get better, I already admit they are better than the Win7/8/8.1 days.
Mine changes. It lists things when I first install them, then later they stop showing up, even though they haven't been modified.
Same here. Who knows.. now maybe it's fixed.. in the last week I haven't had any search issues, but I definitely did in the past, the recent past.
-
I think I've searched this week, but I'm not sure when. Maybe it has been two weeks. The Windows laptop has been off for a while, maybe ten days?
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Dashrender said in Windows: Finding Files with PowerShell:
The experiences of Windows 10 across users is so radically different it's amazing it's even the same OS.
I haven't had any major issues with 1607 (that I know of) But you can read all over the interwebs about how horrible it is.
I'm glad it's working great for those that it is.
It's true. It seems that everyone is seeing something different.
You and @Dashrender. That's two people, not everyone.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Dashrender said in Windows: Finding Files with PowerShell:
The experiences of Windows 10 across users is so radically different it's amazing it's even the same OS.
I haven't had any major issues with 1607 (that I know of) But you can read all over the interwebs about how horrible it is.
I'm glad it's working great for those that it is.
It's true. It seems that everyone is seeing something different.
You and @Dashrender. That's two people, not everyone.
You see something different from each of us, that's more.
-
@Tim_G sees that you need to modify search options to make it work. You see that you need to use a different tool entirely. We see different results. What two people do you see seeing the same thing, is really the question? From our small sampling here, the only consistency seems to be in the differences.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G sees that you need to modify search options to make it work.
No he doesn't. He writes "I haven't configured anything on my personal PC, and searching is 100% for me"
You see that you need to use a different tool entirely.
No I don't. I don't need to use a different tool. I prefer File Explorer. But the Windows search works perfectly and as designed for me.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G sees that you need to modify search options to make it work.
No he doesn't. He writes "I haven't configured anything on my personal PC, and searching is 100% for me"
He had said that he needed to turn off Bing searches.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
No I don't. I don't need to use a different tool. I prefer File Explorer. But the Windows search works perfectly and as designed for me.
What's the value in the other tool then? And why then the surprise that we want to use the intended tool?
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
If you're talking about a Windows search that is the generic search tool, that searches for applications, web apps etc etc, well, why would you use that to search for files in a specific directory. You wouldn't. You'd use File Explorer.
Here above you acted like we were nuts for using the Windows search tool. I'm looking for installed applications, and it can't find them, routinely.
-
My daughter has a Windows 10 laptop, I'll have to check hers later to see if it exhibits the same issue with searching that mine does for the same application, since one that I know can't be found on mine is also on hers.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G sees that you need to modify search options to make it work.
No he doesn't. He writes "I haven't configured anything on my personal PC, and searching is 100% for me"
He had said that he needed to turn off Bing searches.
If you don't want search to include Bing searches then you turn it off. That's a feature, not a bug.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G sees that you need to modify search options to make it work.
No he doesn't. He writes "I haven't configured anything on my personal PC, and searching is 100% for me"
He had said that he needed to turn off Bing searches.
If you don't want search to include Bing searches then you turn it off. That's a feature, not a bug.
"Feature". It undermines the use cases that Microsoft touted and causes Windows to no longer work as we were told to use it. Yes, you can turn it off. But we should have needed to turn it on. It's a changed interface reaction without a changed interface process. It causes Windows to have been very useful and now be problematic when used in an identical manner. "Needing extra unnecessary management" is not a feature.
-
I get that new versions of software have new features that you don't like. Software evolves. But that's not what you said. You said that everyone is seeing something different.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
I get that new versions of software have new features that you don't like. Software evolves. But that's not what you said. You said that everyone is seeing something different.
Both. It evolves, but there are "new features" and there is "unreliable interfaces", those are not the same. You can add a new feature without creating a situation where old actions no longer produce the same results. It's considered one of the fundamentals of good interface design - keep the same action doing the same thing. Add new "features" of course, but changing an interface is not a feature, it's a change to an old feature.
But seeing things differently is important. What's likely key here is different people searching for different things. I search essentially only for applications and only because Microsoft told me how I was supposed to do this to do things the "Microsoft way" and I adapted. It worked perfectly once I did. From Vista through 8.1 it made things work. The Metro interface was still jarring and totally disruptive to me, but if I closed my eyes and kept working as before, things still worked the same. And on my Linux desktops, all of the ones that I use implement that same Microsoft-recommended interface design. Hit the Windows key, type the name of the application you want to run, hit enter.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
Hit the Windows key, type the name of the application you want to run, hit enter.
But you're the only one claiming that this doesn't work properly.
-
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
Hit the Windows key, type the name of the application you want to run, hit enter.
But you're the only one claiming that this doesn't work properly.
No, if it returns dangerous unpredictable results by default (web results) then it does not work as originally intended and stated by MS. So if you feel web results are in there, then you agree that it does not work the same as before. Originally it was safe that you would never suddenly expose data to the Internet via this process by default. If you accidentally typed a password there, for example, or you just didn't want to publicize what you are looking for on your desktop, it was not a security concern. It's very different today.
So we are agreeing on how it works. You are just saying, I think, that you think it is a feature and I'm saying that I feel that they broken interface that they themselves promoted.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Carnival-Boy said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
Hit the Windows key, type the name of the application you want to run, hit enter.
But you're the only one claiming that this doesn't work properly.
No, if it returns dangerous unpredictable results by default (web results) then it does not work as originally intended and stated by MS. So if you feel web results are in there, then you agree that it does not work the same as before. Originally it was safe that you would never suddenly expose data to the Internet via this process by default. If you accidentally typed a password there, for example, or you just didn't want to publicize what you are looking for on your desktop, it was not a security concern. It's very different today.
So we are agreeing on how it works. You are just saying, I think, that you think it is a feature and I'm saying that I feel that they broken interface that they themselves promoted.
It is working exactly as Microsoft intends. Just because Microsoft changed their intention and you do not like it, does not mean it is not as intended.
But again, I have no issues with it because it shows all of my data correctly when I search for something.
So you have issues with it. Not everyone. You are exaggerating your point of view as total fact when it it is not.
Staying up to date means you accept change. Even if it is a change you do not like.
Implement appropriate security in your applications (search in this case).
If web results are insecure in your application, disable them.
-
@JaredBusch said in Windows: Finding Files with PowerShell:
It is working exactly as Microsoft intends. Just because Microsoft changed their intention and you do not like it, does not mean it is not as intended.
I said as originally intended. It's a changed interface, that was my point. Not that it wasn't intentionally changed.
I'm not the one that brought up the issue here, I only mentioned that I had similar issues to Dash who had been asked what issues he saw.
