Windows 10: Mapped Drive Runtime error 3044

Hello,

I have an issue which I hope somebody can shed some light on. We have an application which was written during the time of Windows XP. This application looks for a Microsoft Access Database file on our server via a mapped drive, for example the path is "G:\Despatch Data".

This software has worked unchanged since windows XP but has continued to work in Vista, Windows 7, Windows 8 and Windows 8.1.

The problem however is Windows 10, if we try and load the software we get the following error......

Run-Time error 3044

'G:\Despatch Data\service.mdb is not a valid path........'

However if I type in the exact same command line into My PC then it works without issue.

Another example of my Mapped Drive madness is also with Opera, if we have for example drive F: mapped to the server, the Opera installer (again designed for XP) cannot find any F: drive. I can then create a mapped drive in Opera (i.e. drive L) which will work however this does not show in My PC as a connected drive. It will also remain available to Opera as drive L until I reboot the PC.


I'm guessing the way in which windows 10 and XP differ in how they store the mapped drive settings and the older software is somehow trying to look-up the path using the old method.

Any advise greatly received.

:)

 

Runtime Broker in build 10586.29 on PC uses 67% of CPU usage with NAS/LAN impact

Hi Arostino

I have the WD "My Cloud" nas (Linux based). Could not resolve runtime broker until I removed all NAS links in Libraries and also removing any mapped drives to the NAS. Today I added mapped drives to my other win 10 PC's folders and the runtime broker is
ok. I believe any mapped drives or libraries to non-indexed folders will cause runtime broker to misbehave. This was not the case before build 10240, so something has changed. Also if I try to re-add nas folders to libraries it will say can not link to non-indexed
folders, but currently I have forgotten how to get around that problem.

 

Problem with Nokia Map loader

Have just upgraded to ver.2.02 from 2.0. due to auto update no choice really :O

Experiencing same problems as you describe, (waiting for device) plus runtime error appears if phone is connected in data mode. Microsoft Visual C++ Runtime Library, Runtime error program: C:\Program Files\Nokia\Nokia Map Loader\map loader.exe abnormal program
termination

Please advise on deleting "Private folder" in storage Mode?

Regards

V