|
To make it sort...
I found out the computer from where the locks originate...
I found event #14 that states, that the password for my account is wrong and I should update it using Credential Manager (but the Credential Manager is empty)
What I can't find is what application/server uses my account on that (not mine at all) computer...
My hint is that it is about a service, as it happens also when no one uses the computer, but in the list there is no service listed with my account...
There is a hint how can I identify the process/application tries to use my account?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Hello,
I am using a portable chat application via LAN which is placed in local server(Windows server 2012) computer say computer1. I have another Windows server(Windows server 2012) PC in which around 10 people are working. Say that pc as computer2. While working in computer2 we used to access chat application from computer1.
Some time I will update the some features of chat application and replace that in computer1 without any error. Now in order to make latest version of application available to the users of computer2, all the working users in computer2 has to close and then open the chat application. This is the procedure which need to be done in order to open the latest version of app,
1.userA and userB are using chat application,
2.userA, userb both closes the application
3.userA, userb opens the app
Here is my problem,
1.userA and userB are using chat application,
2.userA closes the application but userB still kept that app open.
3.userA opens the app, here userA will get old version instead of new version which is available in computer1.
Why this is happening ? Where windows store the cache ? Is it not possible to make that application to load newer version when a other user is kept open that ? I know I can follow method1 as solution, but it is very difficult to know that all the users are closed the app so that I can inform again to open it.
Please help me.
|
|
|
|
|
srikrishnathanthri wrote:
Why this is happening ?
Because you can't overwrite a file that is in use.
srikrishnathanthri wrote: Is it not possible to make that application to load newer version when a other user is kept open that ?
Sure; don't overwrite the previous version.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
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.
modified 6-Jun-16 12:35pm.
|
|
|
|
|
xiecsuk wrote: Cannot open c:\ProgramData\packard bell\updater2\updater2.xml
That should give you a clue - is this a Packard Bell system?
|
|
|
|
|
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.
|
|
|
|
|
Well I guess you have something in there from your old HDD that you were not aware of.
|
|
|
|
|
Wow, I haven't seen a Packard Bell in 15 years! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
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!
|
|
|
|
|
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!
|
|
|
|
|
it sounds like it may be a possible running task.
Check the Scheduled task for a script running.
This was what showed up in a pop up Command window ?
|
|
|
|
|
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...
|
|
|
|
|
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
|
|
|
|
|
Thanks for that. Looked at the hidden folders, but didn't learn much other than it is correct - those files are not there.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
Quote: I would strongly suggest option 2
I agree. Considering the time he already spent, he probably could have done a clean install by now!
Get me coffee and no one gets hurt!
|
|
|
|
|
I have had a new system built but I didn't include any hard drives; I moved them over from my old machine. Everything seems to be good as far as they are concerned. Win10 boots OK off the C: drive; all my other apps open successfully off C:; and my data is available on the D: and E: drives.
However, I had a SSD installed in the new machine onto which I intend to transfer the WIN10 image on my current C: drive. However, although the SSD is displayed in the BIOS list of drives and in Computer Management\Device Manager\Disk Drives, it is not displayed as a drive letter in File Explorer.
Does anyone know how I can get it recognised by File Explorer?
|
|
|
|
|
I'm not 100% sure that Win10 has the disk management util, but I expect that it would.
Here's the steps that work in 7/8
1. Open MMC as admin
2. File -> "Add/Remove Snap-In..."
3. Select "Disk Management"
4. Select the drive
5. Right-click and choose "Change Drive Letters and Paths..."
It's pretty self-explanatory at that point.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Thank you for your help. I couldn't perform stage 5 but I did manage to find a way to format the drive correctly and set a drive letter at the same time. I can now transfer my existing system onto it when I am ready.
|
|
|
|
|
xiecsuk wrote: I had a SSD installed in the new machine onto which I intend to transfer the WIN10 image on my current C: drive.
You might want to take a look at AOMEI Partition Assistant[^] - it apparently includes a wizard to do precisely that.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
