Windows 10 Search
-
@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.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Carnival-Boy said in Windows: Finding Files with PowerShell:
I've no idea what you're talking about. I've never had an issue with the search in the standard File Explorer. It's always returned exactly what I'm looking for, and I haven't noticed it changing much over the years. I've never had it do a web search.
I'd say for me it fails around 50% of the time. I type in the name of the application I need to run and instead of finding it, it populated Bing information when clearly I can see the thing that I need to run right there on the desktop with the right name!
Then I have to ask, why do you still have that turned on?
Should I have to configure basic use of the menu? I don't use Windows often, on any other OS it "just works." I was following MS' stated convention. It's important to know if their "as designed" system works or not. Or what it does.
How often does it drop to bing search? I think I've only had it happen once, annoying sure but not something that bothers me overly much.
-
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Tim_G said in Windows: Finding Files with PowerShell:
@scottalanmiller said in Windows: Finding Files with PowerShell:
@Carnival-Boy said in Windows: Finding Files with PowerShell:
I've no idea what you're talking about. I've never had an issue with the search in the standard File Explorer. It's always returned exactly what I'm looking for, and I haven't noticed it changing much over the years. I've never had it do a web search.
I'd say for me it fails around 50% of the time. I type in the name of the application I need to run and instead of finding it, it populated Bing information when clearly I can see the thing that I need to run right there on the desktop with the right name!
Then I have to ask, why do you still have that turned on?
Should I have to configure basic use of the menu? I don't use Windows often, on any other OS it "just works." I was following MS' stated convention. It's important to know if their "as designed" system works or not. Or what it does.
That's a good point. It 'should' "just work". Like everything in IT, right? As advertised.
Haha... I know what you mean though, and I do agree. But no, you shouldn't have to configure anything. I haven't configured anything on my personal PC, and searching is 100% for me. If I search for an App I have installed, it comes up. It may also show Bing crap down below, but if the app is installed, I can't think of any reason why it wouldn't show up. That's never been the case for me.
Same with files, if I search for a file, and click the document icon at the top of start, it finds it.
I suppose it shouldn't be the way it is for you, and I can't imagine why it's like that for you. I guess you'd have to take a video of what you are searching for. Show in the video where it is, then show you searching for it. I'm curious to see an example.
-
To continue using @Tim_G's example of
GetNetAdapterVmq, @scottalanmiller, search does work perfectly as designed because they designed it with a damned button for finding files only.
-
@JaredBusch Here's a real example, both ways for my example (excluding the bing results, because it's turned off via GPO):
-
Hit start/windows key --> typed 'get-net':
-
Same as above, but this time I clicked the "Find results in documents" button:
-
-
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.
-
@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.
Check your indexing settings. Windows does not index everything by default.
My Windows 10 machine did not find my documents initially because I changed the default location and did not add it to the indexed location list.
So problem caused by user. -
@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.
