Windows 10: Users reporting false 'Out of Memory' errors when moving a shortcut

Several MSDN developer forums have asked me to move this issue to a Windows forum since it seems to be a Windows 10 issue. We have complaints from our users about an 'Out of Memory' message from Windows, but they are not out of memory and just moving a shortcut.

Short version:

-----------------

First, I create a "msi" via "VS Setup Project" and create the corresponding shortcut on Desktop.

Next, I cut the shortcut to "Program Files" or "Program Files(x86)".

Then, If I want to move/cut the shortcut back to Desktop, it will show the warning:



If I copy the shortcut, paste it to Desktop and delete the one in "Program Files", it works.

After this, the same cut operation will not occur warning again.

Long version:

-----------------

I have a number of installations using Visual Studio setup and deployment. These installations create shortcuts on the desktop for the user. I have some users who have decided to move these shortcuts into other folders, any of the /Program Files/ folders for example. Besides the fact that they should not be doing this, they discovered that if they then try to move the shortcut back to the desktop, it does not move and they get an "Out of memory" message when they clearly are not out of memory. I can readily reproduce the message as well, although not with all shortcuts...but especially the ones created by the installer.

So, I think there is something about these shortcuts (perhaps permissions) that Win10 does not understand and is throwing a strange message. I don't do anything fancy with the definition of the shortcuts...in fact, there aren't many properties to define for them in setup and deployment.

So, is this a problem with the shortcut, the way Windows 10 handles them, or both? It does seem like an incorrect user message. Any suggestions to resolve? At the very least it may help to know why this happens and perhaps pass it on if it is a Win 10 issue.

Thanks,

Peter

:)

 

False positive for desktop shortcut scanner.lnk

The 1.239.488.0 virus / spyware definition update that rolled out about 24 hours ago appears to be producing a false positive for any shortcut placed on the desktop called "Scanner.lnk". I can consistently replicate a false positive for Trojan:Win32/FakeSysdef
with the following steps.

• Create a shortcut to an exe file.
• Place the shortcut on the desktop.
• Name the shortcut "Scanner".
• Run "Quick Scan".

I don't get the same result by directly scanning the file, nor by uploading the file to www.virustotal.com, so it would appear this is as a result of a heuristic rather than a file content analysis. I also don't get the same result with a shortcut that links
to a website.

Can anyone else replicate? How can we go about getting the Windows Defender team to reconsider this heuristic? It's a bit heavy-handed.

 

shortcuts for all users

Hi,

Thank you for updating us on the issue.

To understand the issue better, I would like to know are you trying to create shortcut for all user?

If you are trying to create shortcut for all user try the below steps and check.

• 
  Click on start menu and select
  file explorer.
  
• 
  Click on OS(C and click on user folder.
  
• 
  Click on view on top of the right pane and check on
  Hidden item box.
  
• 
  Now you can copy and paste the shortcut that you want on the folder.
  

Hope it this helps. If you need further assistance with Windows, let us know and will be glad to help.

 

False Reports...

Me and my friends keep getting false reported by somebody but i don't know how to report it to someone working for xbox, could you help me please...