OSSelector adds permanetly new OS (that does'nt exist)

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 6

Hi,
I have Osselector installed with two Win 7 Setups on two different Partitions on the same Drive.
Everytime I start OSSelector from Windows it adds a new Operating System, that in reality doesnt exist.
So I got my two Windows Versions and a lot of non existing Ooperating Systems.
The Problem is, OSSelector sets allways the latetest added OS as default.
If I delete these fault Operating Systems the come back next Start, each start one new OS.
Can anyone help?

Thanx a lot
Marianne

Sun, 02/05/2012 - 11:54
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 45
Comments: 4263

If you don't delete the new entry does OSS still add another one? If not, one solution is to just hide the incorrectly detected entry. This keeps it from showing up in the menu and, since it still exists, OSS from thinking it needs to add it again.

Otherwise, are the added entries bootable? Do they point to one or both of the existing installations?

You might check the BCD files of both systems (assuming they are booting independently) and see if both Windows 7 systems show up in both BCD files. If they do, you could try removing the unnecessary entries and see if that helps.

Mon, 02/06/2012 - 17:59
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 6

hI mUDcRAB;
and thankyou for your post.
OSS still adds one new System (that can't boot, because it only consists of a empty 'Windows' folder and the 'Boot' folder with allways the same contents) after each boot, so if I don't delete this, I got a hundred of them.
BCD have only the correspondenting System as bootoption in both Versions.
???
Marianne

Tue, 02/07/2012 - 09:50
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 45
Comments: 4263

If the each Windows installation is booting from its own partition, you could try generalizing the BCD and seeing if that helps.

For example:

  1. Open an Administrator Command Prompt.
  2. Run the following commands at the prompt:
  3. bcdedit /set {current} device boot <ENTER>
  4. bcdedit /set {current} osdevice boot <ENTER>
  5. bcdedit /set {bootmgr} device boot <ENTER>

Note that this may make OSS and DD 11 unable to determine Windows is on the drive. It may stop the extra detections, though. Before trying this it would be good to have a Windows 7 DVD or System Repair Disc available in case you need it to do a repair.

Tue, 02/07/2012 - 19:27