Windows 7 desktop search mapped drives

The background to this issue is that we have a mapped drive letter which allows colleagues to access shared folders on our file servers. The issues are as follows:. Colleagues with these issues all use Windows 7 machines. Our file server is a Windows R2 machine. Dont create shortcuts to drives within drives, the reason is Windows tries to index these drives and if you end up with a circular reference, you have a small nightmare on your hands.

How is the user moving around the tree structure? Many thanks for your reply. Sorry but the shortcuts aren't created within the mapped drives. The shortcuts are on the user's desktop. They create them by navigating to the parent folder and then right-clicking on the target folder and then selecting Send To Desktop as a shortcut.

As for issue 1, the issue happens purely by navigating down the folder tree by double-clicking on a folder then another. All of a sudden Windows Explorer starts moving back up the tree automatically. At no point is the back or move up a folder button pressed. The commonality would be the server itself Any unusual event viewer entries? Has it been scanned for malware? I am wondering, when it begins going back up the folder tree automatically Thanks for your reply.

The reason i think it's a Windows 7 issue is that we have just commisioned the file server as a replacement for our old fileserver. The same issue was occurring with that server too hence that's why I don't believe it's a server issue. There is no rhyme or reason for Windows Explorer to start automatically navigating back up the folder tree.

Note: Any data files that are infected may only be cleaned by deleting the file entirely, which means there is a potential for data loss. Hello all, I have a problem I can not seem to track an answer down for: Recently, I have noticed that Windows Explorer Search is not working when I attempt to perform a search on the entire computer ie: enter a search into the box while in Windows Explorer "Computer" window. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

I have the same question 2. Report abuse. Details required :. Cancel Submit. Hi, I would suggest you to perform the methods given below and check if it helps. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to A. User's post on June 18, Not available in x64 FYI. Jordan W. Stephen Short Stephen Short 46 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. Server is SBS by the way. Have looked through event viewer but couldn't find anything obvious.

Anybody ever come across this? Really want to avoid rebuilding this machine. Any help would be really appreciated, cheers. I've had this issue in the past when my DC was Server The Windows 10 PCs could not search the network drives no matter what I tried. It has since been replaced with a server and the search works fine now. If this is successful, you are logged into the remote machine.

You should then be able to do something like this:. Try finding from a command prompt. That will tell you if it's access to the drive that's a problem or the search service. This will make them show up. Set it to auto and started both Function Discovery services up as they were both running on my machine , rebooted but still the same. Set it to 1 just to see anyway, still nothing. Anything else you can think of? I'm searching for anything. It won't pick up any file names at all, even when I'm in a certain folder and I can see the file there.

I did try a wildcard search as I hadn't before. Strange thing was, it seemed to really "chug" when it was searching a large directory with a wildcard. As in, the green search bar that slowly scrolls across the directory path when you do a search seemed to be going slower and trying harder if you know what I mean, like it was actually picking something up. I honestly thought it was going to show something when it finished but instead I got the usual "Working on it