Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

FFIND weirdness?

vefatica

vefatica

May
13,738
209
After finding the first file (which is correct) FIND is appending "1cd\f\mousocoreworker.exe" to the name of every file found subsequently.

Code: 
v:\> ffind /s /a: c:\MoUsoCoreWorker.exe
C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5131.1.17\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\f\mousocoreworker.exe
C:\Windows\System32\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.4957_none_fb4b665739de2d96\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.4957_none_fb4b665739de2d96\f\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.4957_none_fb4b665739de2d96\r\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\f\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\r\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\f\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\r\MoUsoCoreWorker.exe1cd\f\mousocoreworker.exe
 
I don't understand that.

IMHO ffind is right, because at the end it's always mousocoreworker.exe

Why should ffind not find/display it?

Ahh, you meant really the unnecessary appending! Yes, that's indeed weird. This doesn't happens here!

Code: 
ffind /s /a: c:\MoUsoCoreWorker.exe
C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5131.1.17\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\f\mousocoreworker.exe
C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.5247.1.14\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\f\mousocoreworker.exe
C:\Windows\System32\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\f\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5072_none_fbaf2a053992e1cd\r\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\f\MoUsoCoreWorker.exe
C:\Windows\WinSxS\amd64_microsoft-windows-u..te-orchestratorcore_31bf3856ad364e35_10.0.19041.5198_none_fba5d1fd3999ca32\r\MoUsoCoreWorker.exe

I used Beta 34.0.14 and you?
 
TCC 34.00.14 x64 Windows 10 [Version 10.0.19045.5247]

I restarted TCC and it's not doing it now.
 
Hmmm! I can make it happen.

First, in a "normal" console, showing the first three files..

1736733797108.webp


Now resize (with the mouse, from 128 columns to 92 columns). Try FFIND again; the output is different!

1736734018372.webp


This may not be FFIND, but rather a resizing-the-console problem. I'll test.
 
I tried (with DIR and FSEARCH) and could not reproduce this or anything similar.
 
vefatica said:
Hmmm! I can make it happen.

First, in a "normal" console, showing the first three files..

View attachment 4832

Now resize (with the mouse, from 128 columns to 92 columns). Try FFIND again; the output is different!

View attachment 4833

This may not be FFIND, but rather a resizing-the-console problem. I'll test.
Click to expand...

Not reproducible here, before or after resizing the console window.

FFIND doesn't know anything about the window size (unless you also using the /P option); it's just sending the output string to Windows (via WriteConsole).
 
As I said, I can reproduce this at will. It seems to have something to do with using few enough columns so those first files, originally wrapping to a second line, now wrap to a third line. Heres my most recent test (showing only four files). First, default 128 columns.

1736782437341.webp


Now I'll reduce the number of columns (to 105) but not so much that more lines are required.

1736782598117.webp


Now I'll reduce the number of columns (to 102); more lines are needed and corruption begins (see the fourth file);

1736782771583.webp


Two notes:

1. I cannot reproduce this with v33.
2. If I try to limit the output by piping to HEAD /N 4 there is no corruption.
3. That resembles the output from post #4 in that the added corruption (in this case, "exe") is what appears at character 2 in the wrapped lines above. As in this one, the added corruption being "1cd\f\mousocoreworker.exe"

1736783471088.webp
 
There's another oddball thing happening. Last night, the FFIND test was finding one file is c:\windows\servicing (see post #1). Today it's finding three!
 
First, yes I thought it could be something with breaking lines (wrapping), resizing (window) or something like that instead of FFIND itself. Thanks for finding out - and also for the details! Till now, I can't reproduce it (v34.0.14).

Then about the different findings: that is very weird! Will make some tests here too ...
have you any news about that, Vince? You searched for files which I could have too here (OS files or so), so I could also test it? Ahh, you said it in "servicing" ... will test that ...
 
Last edited:
I had 2 finds for/in "servicing" and still have 2 ...
 
Ah, yep, I see - thanks.

What a mystery! And I'm running out of ideas right now...

I mean it's a backup folder for cumulative updates BUT these files are from older cumulative updates and why in the world does it first find 1 and now 3??? That of course is exactly your question, I know ... I just had to repeat it because this is one of the biggest mystery ever for me related to a TCC command ...
 
This is somewhat better. The extra text is gone but now there are missing characters. The first command below finds files named MoUsoCoeWorker.exe (missing 'r') and MoUsoCoreorker.exe (missing 'w'); the second one finds mousocoreworker.ee (missing 'x').

1736964965774.webp
 
On the theory that this is not really an FFIND issue, I tried dir /a /s /f c:\mousocoreworker.exe several times; did not find any errors in the output.

Then I added a /D to disable directory coloring, and hey presto... missing characters. Most often the final backslash, occasionally the first O.
 
Charles Dye said:
On the theory that this is not really an FFIND issue, I tried dir /a /s /f c:\mousocoreworker.exe
Click to expand...

I don't have any coloration. Even without /D I get several files name MoUsoCoeWorker.exe (missing 'r').
 
Before build .17 it was good HERE, NOW I have also the problems with missing char ... and also even without /D ...

Here a missing "o" "MUsoCoreWorker.exe" instead "MoUsoCoreWorker.exe"
 
Seems, build 18 fixes this with missing chars in ffind too!

Thanks!
 
You must log in or register to reply here.
Back
Top