Every time when open my file explorer and perform some operation it get stuck and starts buffering this problem has started to happen after when installed an solid state drive from a local store went to many stores but they were not able to fix it although tried many drivers but it's not helpful for me thanks in advance for helping me.
Related
I have a real problem, that started from yesterday. I was using my Dell Laptop until I found something called sc, after making my laptop on sleep mode, I tried to get out some piece that I discovered it was for ssd, when I returned it correctly and tried to turn on my laptop again, it showed me the blue screen with a stop code : >"inaccessible boot device".
after a day, I tried to open it again, but nothing happened, I tried alot, searching the internet about the matter but nothing. I also asked someone I know and he told me that ghe laptop needs some format.
Please, Help me finding a solution, because I don't want to format, lots of informations and apps are installed in it, also, there are lots of projects I finished and there is a very important project I am working on, please, help me find a solution without format, and thanks.
Everytime I start up my laptop, I get the following error:
Can't find file C:\Users\robert\AppData\Roaming\Microsoft\Windows\dhisevfi\eieteifb.exe Check if you have the entered the name correctly and try again after.
I can't find this .exe file anywhere on my laptop and even on the internet it can not be found. Check here to see the image of the error.
StackOverflow is my last resort to solve this problem since no one seems to understand why it happens.
I would be very grateful if someone could me out a bit further.
Thanks in advance!
Robert
I've just searched the internet and I didn't find the name of this executable, which most likely means that it has been generated automatically, which is a typical situation for ... a virus! (I had a similar situation several years ago)
So, apparently your computer has been infected with a virus, the corresponding executable is not (longer) present on your computer, but your computer (still) wants to launch it. (Don't worry: as the executable is not there anymore, there won't be any harm to your computer anymore)
I'd advise you to remove this entry from your startup folder, but this action depends on your Windows version. There are lots of entries about this subject all over the internet.
I have designed and built a database in MS Access 2013. There is a back end file on a shared drive and multiple users use a front end located on their individual PCs.
Occasionally, seemingly randomly, the back end will lock out in read only mode, meaning that none of the front ends can update the back end, and when I open the Back End, I get the yellow bar saying:
"READ-ONLY This database has been opened read-only. You can only change data in linked tables. To make design changes, save a copy of the database".
It won't let you save a copy of the database by the way. Other databases in the same location open correctly.
I have some spreadsheets that access the database read only, occasionally these change to Share Deny Write, and when they do you get the 1kb lock file for the database. This allows me to see who has it locked out. In my case, this file doesn't appear until I open the database read only and then it shows as locked out to me.
Eventually, it tends to just fix itself, but it can take hours and I have no idea what happened to fix it!
I've searched Google and tried everything that's been suggested, and of course restarted my PC a couple of time, none of which fixed it. However, last time this happen, after restating my PC it worked again, could have been a coincidence.
Any advise about how I can see who's locked it, or how I can get it to unlock would be greatly appreciated so we don't have hours of downtime!
As far as I can detect all machines are the same that excelDna is being used on.
On one specific machine I tried to use the code I have created, and ran into an issue. Logically I thought this was odd and instead tried to add a sample file that comes with the download.
So now, I am trying Errors.xll/Errors.dna that come as a sample. The same error occurrs. Therefore to me there is an issue on this specific machine.
The error I am receiving is "a problem occurred while an add-in was being initialized (InitialIntegration failed). The add-in is built with ExcelDna and is being loaded from P:\xlDna\Distribution\Errors.xll"
Has anyone encountered this? Help needed to understand why this is happening as it seems quite opaque to debug.
Hi what solved this for me was moving the xll and DNA to the users c:. Once located on the c: worked flawlessly.
Hope this helps someone else in the future.
How can I find what's hanging all new installations on a Windows box?
While testing an installation script on Windows (XP Pro, if it matters) I've run into a situation wherein any and all attempts to install anything on the system hang waiting on who knows what. When the system is restarted, all queued up attempts at installation then go through their exit paths with pop-ups that report the installation is being aborted due to system shutdown having been requested. Of course, reboots do not cure the problem. The system otherwise runs fine.
So... How can I determine what part of the OS I've wedged? (Something in the registry, I suppose, but I'm a real greenhorn when it comes to Windows.) Most likely, something from a preceding install attempt went awry and is now blocking even though I saw no errors reported. Once I figure this out, I want to put in a check for this sort of thing, possibly at both ends of my install scripts, if that seems reasonable.
Thanks for your input.
UPDATE:
Unfortunately for me, rebuilding from scratch to get to the point the system's in now is about 9 hours. I'd like to unwedge it from where it is now rather than reload (again). Procmon seems great but I haven't got SP2 installed, only SP1! -frown- So, other ideas are welcome.
I assume you've tried logging the install to see where things go wrong?
Try rolling back to before things went wrong using "System Restore", if that doesn't solve it and the MSI log files show nothing useful then I'd take the plunge and reload before wasting any more time on it.
That said, if you're developing installers then taking an image of this PC in it's crappy state could be a worthwhile exercise. Some point in the future when you have more time to debug you can try and figure out what the problem is.
P.S. I'm assuming you're asking this question from the point of view of someone developing an installer and not as a tech-support question... otherwise this question should probably be closed as not-programming-related ;)
Try using Procmon to figure out where the installer is having problems, if you set a filter it will report all file and registry activity for that process.