Does Anyone Know What the Quoted Text Means?
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
If you transfer a system's drive from one machine to a totally different machine, you may run into some issues: Invalid or missing drivers, incorrect registry entries, etc. etc. I will recommend that you do a clean install of Windows 10 on the new machine.
Get me coffee and no one gets hurt!
-
xiecsuk wrote:
Cannot open c:\ProgramData\packard bell\updater2\updater2.xml
That should give you a clue - is this a Packard Bell system?
-
If you transfer a system's drive from one machine to a totally different machine, you may run into some issues: Invalid or missing drivers, incorrect registry entries, etc. etc. I will recommend that you do a clean install of Windows 10 on the new machine.
Get me coffee and no one gets hurt!
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
It's your legacy Packard Bell installed apps trying to update themselves and drivers which are now not used with your new hardware. Have a look in your startup stuff and see if there is anything obvious, and if so - delete it!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
This is a system I specced myself. The Lounge - CodeProject[^] As far as I know, there is nothing in there that remotely resembles Packard Bell.
-
Do you mean just Win10? Or do I have to install all my apps as well? I was hoping to avoid that.
Clean install means installing everything, both system and apps, from scratch on a clean disk. You may be able to avoid a clean install by running Repair from the Windows 10 install disc. I think you can do this with Windows 10, but have never done it myself. Good luck if you choose to avoid a clean install. I have a feeling you will need it. (The luck, that is.) :)
Get me coffee and no one gets hurt!
-
Does anyone know what the following quoted text means? I have just commissioned a new self-specced machine into which I transferred my Win10 system HD from my old machine. I also transferred my data HDs. Everything looks fine and indeed is fine when I run Win10. There appears to be no difference to the system that was running in my old machine; except, that is, for a cmd.exe that is being run occasionally which produces the following output.
Quote:
FINDSTR: Cannot open c:\ProgramData\acer\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\gateway\updater2\updater2.xml The system cannot find the path specified. Cannot access file C:\Program Files\DriverSetupUtility\FUB\+ FINDSTR: Cannot open c:\ProgramData\founder\updater2\updater2.xml The system cannot find the path specified.
I can't understand why it is being run and why it is saying that it can't find the specified paths. Essentially, nothing should have changed on the swapped HD. Hmmm, unless, of course, the installation of the motherboard software and the graphics card software has caused the problem. That is the only new software I have installed.
The C:\ProgramData directory does not appear when I open the listing of my C: drive. So I though I would search for updater2.xml. It appears that ProgramData is a hidden directory on the C: drive and there appears to be no way to open it, which I wanted to do to see what else was in it. I wonder how many other hidden directories there are.
-
The C:\ProgramData directory does not appear when I open the listing of my C: drive. So I though I would search for updater2.xml. It appears that ProgramData is a hidden directory on the C: drive and there appears to be no way to open it, which I wanted to do to see what else was in it. I wonder how many other hidden directories there are.
In Windows Explorer, click "View -> Options" to bring up the Folder Options dialog box. In the "View" tab, under "Advanced settings", select "Show hidden files, folders and drives". While you're in there, make sure the "Hide extensions for known file types" option is un-ticked.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
In Windows Explorer, click "View -> Options" to bring up the Folder Options dialog box. In the "View" tab, under "Advanced settings", select "Show hidden files, folders and drives". While you're in there, make sure the "Hide extensions for known file types" option is un-ticked.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
The C:\ProgramData directory does not appear when I open the listing of my C: drive. So I though I would search for updater2.xml. It appears that ProgramData is a hidden directory on the C: drive and there appears to be no way to open it, which I wanted to do to see what else was in it. I wonder how many other hidden directories there are.
-
If you have administrator access then you should be able to see all hidden directories. I can go straight into C:\ProgramData on my system.
-
Yes, I did go straight into C:\ProgramData on my system. As I said, the files cmd.exe was trying to find weren't there.
It sounds more and more like your system is in a mess. you have one of two options: 1. Keep struggling on trying to find out what is happening with no real idea of where these ghost processes are coming from, or what else might bite you in the future. 2. Do a proper clean install and ensure that you have a stable running system. I would strongly suggest option 2.
-
It sounds more and more like your system is in a mess. you have one of two options: 1. Keep struggling on trying to find out what is happening with no real idea of where these ghost processes are coming from, or what else might bite you in the future. 2. Do a proper clean install and ensure that you have a stable running system. I would strongly suggest option 2.
I hear what you are saying but Win10 and my apps are working exactly as I would expect them to. I am tempted to just ignore the error messages and continue for the time being. After all, they are not causing me any problems that I can tell. I can't face having to install everything from scratch again until I have to.
-
It sounds more and more like your system is in a mess. you have one of two options: 1. Keep struggling on trying to find out what is happening with no real idea of where these ghost processes are coming from, or what else might bite you in the future. 2. Do a proper clean install and ensure that you have a stable running system. I would strongly suggest option 2.
