Solved Getting "Item Not Found" when creating or renaming folders in explorer

[SummGuy]

Getting "Item Not Found" when creating or renaming folders in explorer

I've been using RT7 Lite over the past few months to create a fully updated Win-7 SP1 installation image that includes drivers for the hardware I have, and does not include any of a dozen or so "bad" telemetry or win-10 nagware updates. For the record this is Win-7, Ultimate, SP1, 32 bit. I've rolled in over 550 updates so far, seems to be up-to-date right at first boot as far as WindozeUpdate is concerned.


Problem is that I get a message window every time I create a new folder or rename an existing folder. This is happening when the folder is on the system hard drive (I think it happens on thumb drives as well). The message is that the "Item not found" - in reference to the new name I've just tried to apply. I can select "try again" and that works - all the time. I'd rather not have to deal with that.


I see that this issue started way back in April or May 2010, and there are various threads on the net about adding or deleting registry entries, or that it may be related to one or two KB's, or that it may be related to trying to get rid of this thing called "Libraries" that shows up in file explorer. I've tried everything, and can't make this issue go away.


Any idea what I should be looking for - either in the registry or bad kb's that I should try to remove from my master-install image?

 

[torchwood]

Is search indexing on??

Roy

 

[SummGuy]

I don't see the index service in the service list. That would be because, if I remember correctly, RT7 lite lets you remove services, and this is one that I would have removed, based on everything I've read about it. And the Black Viper service site agrees that this is a useless service, a resource hog. I would have thought that if this service was known to be needed during new-folder creation or folder-renaming, that such an elementary fact would be well known by now.

 

[Layback Bear]

Black Viper can get one in a world of problems.
As far as I know indexing causing no problems using Windows 7. Indexing causing no problems with my systems.

 

[SummGuy]

It's not that I'm trying to indicate that indexing service *causes* problems. In general I like to run a tight ship (when it comes to XP at least) and in the few win-7 systems that I set up for others I also like to see as few services running as possible. Index service is widely commented on as being unnecessary and likely a drain on system performance.


Regardless my reasons for turning it off, it's quite a different story if this service is hooked into necessary system functions (like the one being discussed) in a way that is undocumented or otherwise not widely known.

 

[Layback Bear]

From post #1

For the record this is Win-7, Ultimate, SP1, 32 bit. I've rolled in over 550 updates so far,

Where did you get 550 updates for Windows 7?
That seems extremely high.

 

[SummGuy]

This is a list generated from the command line "wmic qfe" piped to a text file, brought into excel and stripped of all info and reduced to the numeric kb number, sorted by that number. These updates and hotfixes were downloaded using whdownloader and integrated into an install image by RT7lite using Windows 7 Ultimate SP1 32-bit as the base OS. About 2 dozen of the most recent updates were downloaded manually since they are not in the most recent whdownloader list.


557 kb updates.


And PS: I've recompiled another rt7lite installation image, and have re-added the indexing service to the image. After installation I can confirm that the indexing service is running, and I still have the "Item not found" issue when creating or renaming folders.

 

[SummGuy]

I have determined which KB, when integrated alone or with many different combinations of other KB's by RT7 into an original copy of Win-7 Ultimate SP1 32-bit, will result in the system (a) not showing (not having) any Libraries, (b) not being able to create new libraries, and (c) giving an "Item not found" message when creating new folders or renaming existing ones.

The KB responsible for that behavior is 958559.


The interesting thing is that upon manually performing the first WU update check, my test system will download something (1 thing) from MS (some update to the WU update system - which is expected and which wmic does not show btw). That much is expected. But after restarting the system, the missing Libraries (and the ability to create new libraries) comes back, but the "Item not found" message remains. Again, this happens when kb958559 has been integrated into the installation image.