"Error 0x80004005: Unspecified error" when renaming folders in Windows 10

I've managed to mess up windows 10, so it produces quite many odd errors.

One of them - even if you try to create new folder and / or rename existing one - explorer produces an error "Error 0x80004005: Unspecified error"

Problem started to manifest after I have used SHChangeNotify function call (either powershell or C#) by changing RoamingAppData / guid 3EB685DB-65F9-4CF6-A03A-E3EF65729F3D.

Reasking same question as in "Unspecified Error" when renaming folders in Windows 10, because I managed to find an answer to this problem.

Exclude slides from PowerPoint handout

I'm creating lecture presentations in PowerPoint (2010) and would like to be able to exclude some of the slides from the lecture handouts. I would have thought there'd be a 'properties' tab for each slide, and I'd be able to select 'exclude from handout'. Apparently not.

I could just create a second PowerPoint with some of the slides deleted, but this becomes laborious if I decide to make last-minute changes to one of the slides, as I would then need to produce a new handout file. Furthermore, I would like my students to be able to print their own handouts from the PPT file if possible, so specifying a reduced page range when printing is impractical.

I know this is possible it TeX, but I am wedded to Microsoft as this is what the entire department uses.

Any ideas?

Windows 8.1 - USB Autorun not changing the icon

I have created an autorun.inf file with the commands below :

[Autorun]

label = MyName

icon = myicon.ico

The purpose of this autorun file is the change the default name Removable Disk to MyName and to change it's icon to myicon.ico.

Last week it was working well in my Windows 8.1. Yesterday i accidentally unplugged my USB without using safe removal of drive. After that when i plugged in it prompted and said to "Scan and Repair the drive ". I clicked scan and it started but since it was taking too long to scan i cancelled the operation. My intention was to re-run the scan. Then i safely removed my drive and plugged it again. Then i went to "This PC" and looked for the drive. The drive had the default icon. So i performed the scan again and it finished quickly .Then i opened my drive and looked for my autorun.inf and myicon.ico file. It was there and since the name and icon didn't change i removed those two files. Then i created the autorun file and the icon file again and moved to my drive. I unplugged the drive after performing safe removal of the drive. The i plugged it again. Even now its not working as expected. I tried plugging it my other machine running Windows 7 and it worked normally i.e the icon got changed to myicon.ico and the name to MyName.

I check my Autorplay setting and it was enabled. What is to be done to fix the issue?

windows 7 - tring to take read only and write protect of flash drive

I have a 125 GB flash drive that is read only and when i take that off then it goes to write protected. and goes back and forth between the two how can i fix it so it wont be read only and take the write protection off at same time. I have win 7 HP on dell Optiplex 3010 8 GB ram and 500 GB hard drive. i still looking on line for a answer. I have used coomand prompt as administrator and took the read only off then when i try to format then it say's it write protected.

64 bit - Windows 64bit programs incorrectly installed

Okay, this question has ran through my brain for a while but I can't find anything online for it.

I know that on a 64bit version of Windows the 64bit programs are stored in "Program Files", and 32bit programs are stored in "Program Files(x86)" to organize the different programs. However (not really a big issue, more just curious) I have noticed that even when I download a 64bit version of a program (like iTunes) they still (by default) install to "Program Files (x86)"

My question is ... Why?

Is it because the "64bit" programs being stored in 'program files (x86)' are not true 64bit programs ... like dll files still using 32bit architecture?

If the two different folders are not even being put to "full" use then whats the point?

I am just trying to get a clear picture.

Answer

In a nutshell:

The install folder doesn't make a difference

• 32-bit programs can be installed into, and work just fine, in either Program Files or Program Files (x86)




• 64-bit programs can be installed into, and work just fine, in either Program Files or Program Files (x86)

64-bit isn't the same as 64-bit compatible

Some software that is pure 32-bit is advertised as being 64-bit compatible. The way it's advertised can be misleading – you might be lead to believe that the software is actually 64-bit when really it's 32-bit but 64-bit compatible.

Software can comprise of both 32-bit and 64-bit components

This is extremely common. A lot of software is made up of 32-bit and 64-bit DLLs/EXEs. The vendor gets to decide whether the software will install to Program Files or Program Files (x86).

What's the point?

Go figure. I'm sure there was a reason, but so far as I'm concerned the delineation is pointless. I found some info, makes for interesting reading...

http://www.howtogeek.com/129178/why-does-64-bit-windows-need-a-separate-program-files-x86-folder/

linux - Dual boot Arch and Windows 10 with GRUB

I've been using Ubuntu for a while and recently decided to start using Arch. I have both a 120GB SSD and 1TB HDD in my system. When installing Arch on my SSD, I created partitions for /boot /home / (root) as well as a swap partition. I also have Windows 10 installed on my HDD using the default partitions. I would like to be able to dual boot between the 2 operating systems. I installed GRUB to my SSD on /dev/sda, but now when I boot into GRUB, I only see the option to boot into Arch, not Windows. I was wondering how I could boot into Windows via GRUB.

I have a default "/etc/grub.d/40_custom" file:

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries
.  Simply type the
# menu entries you want to add after this comment.  Be care
ful not to change

# the 'exec tail' line above.

When I run "lsblk", I get:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111.8G  0 disk 
├─sda1   8:1    0   200M  0 part /boot
├─sda2   8:2    0    12G  0 part [SWAP]
├─sda3   8:3    0    25G  0 part /

└─sda4   8:4    0  74.6G  0 part /home
sdb      8:16   0 931.5G  0 disk 
├─sdb1   8:17   0   499M  0 part 
├─sdb2   8:18   0   100M  0 part 
├─sdb3   8:19   0    16M  0 part 
└─sdb4   8:20   0 930.9G  0 part

Running "fdisk -l" gives me:

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 47A5839B-C531-4BEE-A083-BD0C5CF4524A

Device       Start        End    Sectors   Size Type
/dev/sdb1     2048    1023999    1021952   499M Windows rec
/dev/sdb2  1024000    1228799     204800   100M EFI System

/dev/sdb3  1228800    1261567      32768    16M Microsoft r
/dev/sdb4  1261568 1953523711 1952262144 930.9G Microsoft b


Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1c797ba1


Device     Boot    Start       End   Sectors  Size Id Type
/dev/sda1           2048    411647    409600  200M 83 Linux
/dev/sda2         411648  25577471  25165824   12G 83 Linux
/dev/sda3       25577472  78006271  52428800   25G 83 Linux
/dev/sda4       78006272 234441647 156435376 74.6G 83 Linux

Any help would be appreciated, thanks!

memory - Unreasonable RAM usage in Windows 7

I have a fresh install of Windows 7, and my RAM in normal startup goes up to 2.5GB. I looked at Task Manager, and there's at least 1.5GB missing from there and in Resource Monitor as well. There's no indication of what's using that RAM. Can someone tell me how I can find out what's consuming my memory? I believe it's a virus, but none of the free antivirus programs tracked it down.

I added the pictures below. If this is normal usage of Windows 7 as some answers imply, then I don't get this at all.

P.S.
My Windows 8 Installation was running below 2.5GB, actually it was 1. something, until recently that I transferred some files from another computer which had the same problem that mine has now. I deleted Windows 8 and installed Windows 7, since I would do that anyway, and now I'm getting high memory usage in Windows 7 as well.

^{(Click images to enlarge)}

Answer

If you want the OS not to use your RAM, take it out of your machine and sit it on your desk. But so long as the RAM is in the machine, using it is free. If you're thinking "I want the RAM free now so I can use it later", you're being silly. You can use it now and use it later. There is no disadvantage to using the RAM. None at all.

Modern operating systems only make RAM free if they have no choice. This is because there are only two things that can happen. If the RAM is used soon, then they just have to make the RAM used again, wasting the effort they went through to make the RAM free -- it is easier to move RAM directly from one use to another. And if the RAM is not used soon, then the effort of making it free is again wasted. Making RAM free is a last resort used only if the OS has no other choice because it adds an extra step the OS will have to go through in order to use the RAM.

Free RAM is only needed for the rare cases where RAM is needed and the operating system cannot transition RAM from one use to another (for example, in interrupt context). Only a very small amount of RAM is needed for this purpose, typically 64MB or so on modern computers. Any more free RAM than that is just waste.

Consider if a program runs and then stops. The program is in RAM. The operating system could make the RAM free or it could keep the program in RAM. If the program runs again soon, keeping it in RAM is a huge win -- disk I/O is avoided. And there is zero cost to keeping the program in RAM if the RAM isn't needed for some other purpose. So the OS keeps the program in RAM until that RAM is needed for something else. Making the RAM free when free RAM isn't needed is a pure losing proposition.