I installed windows 10 on my computer.
Every time I restart my computer, my all new files disappear
and my desktop is empty!!!
Is it a bug or setting issues?
How can I restore my files back
Thanks in advance!
You somehow corrupted your explorer.exe or changed a registry setting :
If you corrupted explorer.exe, best bet is to do a repair or system restore.
To check if explorer.exe is set to your shell:
Ctrl+Alt+Del to bring up task manager. Click File>Run new Task.
Type REGEDIT, click ok.
Click the plus sign (navigate through) entries:
-HKEY_LOCAL_MACHINE
-SOFTWARE
-MICROSOFT
-WINDOWS NT
-CurrentVersion
Click the folder WINLOGON
in the box to your right, find the entry Shell.
If the data correspondig to it is not Explorer.exe, double click Shell and modify it to Explorer.exe.
Close the registry,
Ctrl+Alt+Del to bring up Task Manager.
File>New Task. Type explorer,
click ok.
I think something is gone wrong by the installation. You can look for the files in C:/users/"you username"/desktop if they arent show there you can try other users in the /user/ directory. Maybe you have a bit of luck and the files are stored by the wrong user by some weird reason.
In the most cases the best solution is to reinstal Windows 10. I think it is faster than looking for an solution. (when you havent install a lot of software)
How you can restore your windows (clean instal) it is explained in this video:
https://www.youtube.com/watch?v=qzTNjs8k15Q
Make sure you have an backup from your data ;-)
(sorry for bad english, iam from holland ;-) )
yes it looks like the installation process has not been taken place properly without any interruptions.
The most convenient solution in my experience is:-
1.search locally 'recovery options'through windows 10 search icon on the left bottom corner
2.click "get started" button under "reset my pc".
3.select the option "keep my files".
then once you are safely back in windows 7, again start the process of updating to windows 10 in a fresh manner WITH the pc plugged in to power and with a stable internet connection.
Related
All of the sudden the method by apps open the "select a file" dialog stopped working. For instance if I go to https://uploadfiles.io/, clicking on it does nothing, but the drag and drop works.
This is happening for apps as well, for example I just needed to resync my Google Drive and change the folder location, clicking in "browse" to select a folder does nothing. However, going to Notepad and file > open file works.
I've been searching for a while for the method, .dll, or something that is responsible for this without success. Anyone with a similar issue or more knowledge than what I have can point me in the right direction?
I'm not a naive English speaker so I am not sure if I'm not finding anything because I am not using the right names to search for it.
Windows 10 64b INSIDER PREVIEW FAST RING
I have exactly the same issue. It started somewhere between Friday and today. (Computer was shutdown for two weeks until friday night and before shutting down the problem did not exist.) I suspect some update. In addition to the mentioned issue I have trouble downloading files through Chrome. Edge and IE are downloading fine. Firefox will be installed to test this. It is consistent which apps are (not) allowed to spawn new windows. Apps in 'Program Files' seem OK while those in 'Program Files(x86)' differ. Of those in the (x86) folder OpenOffice is allowed to open a browse window, Adobe Reader is not. KeePass is allowed to open files, EventGhost is not. (changing install folder does not make a difference).
Since it is not clear how long this issue has been around I am hesitant to do a system restore. Also I believe that is a bandaid, not a solution. I am on the Fast Ring of updates.
Been trying to find a way to do this for a while.
Opening a link in an windows explorer window instead of a browser.
For example using this link : ftp://username:pass#ftp.domain.com:80
And opening it in Windows Explorer.
Is it possible to dictate how windows should react when clicking on that link in a email ?
Thank you Fabian H!
Your solution works fine for me :-)
I made just a small change to your code, infact I wrote:
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\explorer.exe" %1
Instead of:
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\\explorer.exe %1"
This second one didn't work for me :-(
But now I can finally enjoy using explorer.exe as the default FTP Client!!
PS:
Tested on WIndows 7
Save these lines in a file with a file name ending .reg and double klick the file:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\command]
#="C:\\Windows\\explorer.exe %1"
[HKEY_CLASSES_ROOT\IE.FTP\shell\open\ddeexec\Application]
#="Explorer"
Tested on WIndows 8.1 64bit.
Thanks to Perneel for his link.
The Windows registry keys shown before didn't work for me, but this works:
HKEY_CURRENT_USER\Software\Microsoft\FTP
Use Web Based FTP = "yes"
Just change value to "no".
(Windows 7 Pro x64)
I was fumbling around looking for how to do this and I ultimately decided to go with the "Add Network Location" wizard method as described here by "nhinkle".
However after doing so, I got a link that generated this shortcut:
ftp://MYFTP_LOGINID#FTPADDRESS/Some/Folder/Navigation/&Stuff/
More what it actually looks like:
ftp://123445_65432#78.13.223.184/root/main/servers/current/
Then was prompted for my login credentials, and thats it. Does not open in Chrome and I just did Send To > Desktop (shortcut) and moved that shortcut to the folder I wanted it in. Now I can open the FTP location from explorer by hitting the link instead of typing the address into the address bar, and it is not opening up in any internet browsers.
I only have one ftp account, dont know much about any background magic that the wizard may have done regarding registry/etc, and I feel like deleting the shortcut wont really undo any of that if it did happen, so if someone could test this and confirm whether or not it works, that'd be great.
Just my 2c :)
HKCU\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\ftp\UserChoice
Check it out, i got the above answer working by deleting this entry
For regularly used FTP sites, if you don't want to make registry edits, create a shortcut using the following format and your site will open in Windows Explorer.
%windir%\explorer.exe ftp://
I have just set up a Guest Windows 2008 R2 Standard Edition 64bit (VirtualBox on Windows 7 64 bit host) for some testing.
I have found that while "inside" the remote desktop environment (i.e. I remote onto the guest ip from the host) that copy and paste does not work. When I say "does not work" let me be explicit.
Assume I am logged onto the Win2008 machine via RDC
Nothing is in the copy/paste buffer. I can mouse click some text and then rclick copy. I can then right click and click "paste" but nothing happens. I can see the "choice" is enabled to paste bu nothing happens. The caret stays put.
CTRL+C / CTRL-V / CTRL-X does not work in RDC land
I am not talking about going in-between copy/paste RDC land/host land.
HERE is the double whammy: when I do the above it then "infects" my host pc so that copy paste is unavailable there too. if PRT SCR doesn't work any more.
I have tried:
restarting the guest os and host os
in group policy editor I have disabled "do not allow clip board redirection" ( I can't give you the full path to this copy/paste just broke again)
I have made sure that in RDC "options" for local resources include clipboard.
NB: if I don't touch RDC at all and log into the guest OS via the console copy paste works perfectly
Kill the rdpclip.exe process using the Task Manager. Then, create a new process named rdpclip.exe. This will solve your problem.
Follow these steps in Remote Machine.
Stop the rdpclip process
Open Task Manager.
Go to process tab and find rdpclip
Choose rdpclip and End that task.
Start rdpclip.exe
Go to start menu and open Run command
Open rdpclip.exe and click Ok button.
Copy paste should work now.
it appears this is a flaw with VirtualBox
these posts covers it
https://forums.virtualbox.org/viewtopic.php?f=6&t=44498 (read the last post)
https://github.com/FreeRDP/FreeRDP/issues/230
(In VirtualBox) SETTINGS->GENERAL->[Advanced]->Shared Clipboard {disabled}
There are multiple things to check.
Restarting rdpclip.exe is a worthy try if the copy/paste fails sporadically, meaning we might on a process in a previous session.
On the client side, we check the RDP Options. Click on the Show Options button in the bottom, pick the third tab Local Resources. Make sure Clipboard is checked.
On the remote server side, we want to check Remote Desktop Session Host Configuration (Win Server 2008+).
Double click the connection to open its Properties window.
In the tab named Client Settings, Make sure Clipboard is not disabled.
We need to log off from the remote desktop.
Workaround
Use an online shared text box like this one:
https://pastebin.com/
I got this tip from a website that "shift + right click" on a folder in explorer in win7 will give us a context menu option by which I can open command prompt right there.
I am looking for a hack that can make this simpler so that whenever I "right click" on a folder in explorer, I always get that "shift + right click" effect.
I am not looking for any info on powertoys.
I need help on exactly what I said above; there has to be some registry hack that makes that "shift" default for every right click on the folder name.
Delete the registry key HKCR\Directory\shell\cmd\Extended. It works for me on the 64-bit version of Windows 7 Ultimate.
http://www.addictivetips.com/windows-tips/windows-7-elevated-command-prompt-in-context-menu/ says you also need to delete HKCR\Drive\shell\cmd\Extended if you want the same to apply for drives shown in Computer, and HKCR\Directory\Background\shell\cmd\Extended for the empty space inside a folder window.
I also had the same question about viewing the cmd prompt without the key combination recently. I am on Windows 8.1 and found that PleaseStand's solution works perfectly.
PleaseStand's solution mentioned worked great for me:
Delete the registry key HKCR\Directory\shell\cmd\Extended.
It works for me on the 64-bit version of Windows 7 Ultimate.
This says you also need to delete HKCR\Drive\shell\cmd\Extended if you want the same to apply for drives shown in Computer,
And HKCR\Directory\Background\shell\cmd\Extended for the empty space inside a folder window.
I might add to anyone who might wonder, HKCR means HKEY_CLASSES_ROOT
This problem crops up every now and then at work. Our build machine can have it's files accessed via a normal windows file share. If someone browses a folder remotely on the machine, and leaves the window open overnight, then the build fails (as it has done now). The explorer window left opened points at one of the sub folders in the source tree. The build deletes the source, and does a clean checkout before building. The delete is failing.
Right now, I'd like to get the build to work. I'm logged in from home, and I'd rather not reboot the build machine. I'm unable to get hold of the person whose machine is looking and the files, and I can't remotely reboot their machine.
When a windows share has a lock, the locking process is System, so I don't think I can kill it, as with normal locks.
Does anyone know a way to release the lock on a shared folder without having to reboot the machine?
If you are admin on the server sharing the file over the network, you can use the Windows in-built feature:
Start → My Computer → Right-click → Manage gets you to the Computer
Management console
In the left nav, navigate to Systems Tools → Shared Folders
You can view Shares, Sessions & Open Files here. This allows you to find out who has opened which files from which workstations.
Right-click on an item in the list to be able to remove the file lock.
Hope this helps.
Found a solution.
Find the process using Process Explorer:
Download and extract procexp.exe
In Process Explorer use the "Find Handle or DLL..." command from the "Find" menu
Enter in the name of the directory which is having trouble deleting
A list of open files which match that name should be shown. Take some guesses and find which one is failing to be deleted. If the file is locked by a windows share, the process holding the file will be System
Note down the directory which was left open
Download and install the Unlocker (Warning: Link removed, as it contains malware)
Install Unlocker, disabling the option for Explorer extensions and other junk
Unlock the directory
Open up a cmd window, and navigate to C:\Program Files\Unlocker
From the cmd window, run Unlocker.exe "the-path-to-the-locked-folder"
A dialog will pop up confirming the lock release. Use the unlock button to unlock the file
Now the directory should be unlocked, and can now be deleted.
Try Process Hacker:
https://wj32.org/processhacker/
Process hacker is like Process Explorer on steroids.
To find the offending process, press CTRL+F or click the "Find Handles of DLLs" button and search for the file name.
Once you find the file in the find handles dialog, you can simply right click the file there and choose "close". (at least for v2.39.124)
Older versions had a "terminator" option in the context menu of the process.
Right click on the offending process --> Miscellaneous --> Terminator --> Select termination techniques. Note that some are possibly dangerous and may have unintended consequences.
I've had similar problems, and none of these suggestions I've seen above look suitable for automated overnight builds (as the original poster implied) because they all require manual effort to hunt down and kill the locks.
The only method I've tried that seems to work reliably is to remove the share itself, make the build, then add the share back. Here's one way of removing the share automatically:
D:\Projects>net share Projects /DELETE /Y
Users have open files on Projects. Continuing the operation will force the files closed.
Projects was deleted successfully.
(NOTE: Creating the share again automatically can be a pain if the privilege groups you need to give it are messy.)
The way i do it is by using both OpenFiles.exe and Handle.exe
You can run them in any order and you will have your resource fully unlocked.
OpenFiles: to disconnect File Sharing sessions
Handle.exe: to release any open handles (don't try to close handles belonging to pid4, since that's the system process)
You can automate this by using powershell, batch, or any language of your choice.
Another option is, starting from Windows Vista, to use the Windows tool built into the system:
monitor resources: perfmon.exe /res
Extracted from: Http://www.sysadmit.com/2017/06/windows-how-to-know-that-process-has-open-a-file.html