DCrats
asked on
issue with registry---not allowed to merge something into the registry
we have a one line .reg entry we "merge" on our laptops to fix a GPS issue.
have had no trouble with it till now.
a fresh image (and re-image) from our sccm server
Windows 7 Enterprise
we try to merge this .reg fix and get "cannot import C:\xxxxxxxx.reg: Error accessing the registry
it wont run regedit as administrator--doesn't open up at all (but does open in regular mode)
I tried it manually, and it fails (using regedit)
what's going on? I have tried using a admin user and the local admin account
have had no trouble with it till now.
a fresh image (and re-image) from our sccm server
Windows 7 Enterprise
we try to merge this .reg fix and get "cannot import C:\xxxxxxxx.reg: Error accessing the registry
it wont run regedit as administrator--doesn't open up at all (but does open in regular mode)
I tried it manually, and it fails (using regedit)
what's going on? I have tried using a admin user and the local admin account
ASKER
wasn't really a "reinstall" as much as re loading the image we have created fro these laptops.
its verrrrrry odd as I have done about five of these without any issue....using the same image...
I wont be back till tomorrow, but will check this site asap tomorrow morning
its verrrrrry odd as I have done about five of these without any issue....using the same image...
I wont be back till tomorrow, but will check this site asap tomorrow morning
Could be a driver issue on the problem machine that changed the registry homes.
You might also consider re-imaging the problem machine
ASKER
its been reimaged-same thing
Something is different about the target image on this problem computer which is changing where the registry home is for the changed data.
ASKER
good thought-- I will try another--
but I think it will likely continue as all 44 of these laptops are exactly the same :)
I also have a email to our sccm/image folks to see if anything changed on the image
I appreciate the help-- this is driving me nuts--I gotta get these imaged and out.
but I think it will likely continue as all 44 of these laptops are exactly the same :)
I also have a email to our sccm/image folks to see if anything changed on the image
I appreciate the help-- this is driving me nuts--I gotta get these imaged and out.
ASKER
tried another-- same frigging thing!!! arrrggghhgghhhh
tried using both admin accounts!!!!! and nothing has changed on sccm/image side.
I really don't need this right now.... :( :( :(
tried using both admin accounts!!!!! and nothing has changed on sccm/image side.
I really don't need this right now.... :( :( :(
I am not sure what to suggest at this point. The entry does not register because it cannot find the correct spot to be entered.
ASKER
so you are not thinking permissions then?
If you are the admin, then permissions should not get in the way. Never have for me.
ASKER
they never have--- till now. and these are not on domain, so nothing should have been pushed to them either.
One thing you might try with this problem machine is to do a fresh install with Windows 7 (do not use your image). See if that corrects the issue.
ASKER
I may be onto something...will report back after lunch :)
ASKER
Think I gots it.
So, as mentioned this was for a built in GPS system a laptop. The issue was the mouse and GPS would conflict, causing the mouse to jump all over the screen. So in my image instructions, the first step was to go into bios and disable the GPS ----so that the mouse would work during the setup/config of these laptops, after they were imaged.
Step one in the instructions is "disable the gps", and all is good----until you try to merge the .reg "fix" for the gps/mouse issue. (it gives the error above)
The fix came when I enabled the gps--knowing it would cause the mouse jumpie thing. I managed to get the mouse to sit still for a sec and shut down the machine-- I didn't even log on.
Went back into bios and disabled GPS again
Rebooted, logged in, and now the GPS fix works.
Don't ask me why, but its happy now that I turned GPS on, and back off again. Not sure if it did something in registry that let the merge happen or what--not going to investigate further--but suspect windows sees the GPS and adds something to the registry.
So, as mentioned this was for a built in GPS system a laptop. The issue was the mouse and GPS would conflict, causing the mouse to jump all over the screen. So in my image instructions, the first step was to go into bios and disable the GPS ----so that the mouse would work during the setup/config of these laptops, after they were imaged.
Step one in the instructions is "disable the gps", and all is good----until you try to merge the .reg "fix" for the gps/mouse issue. (it gives the error above)
The fix came when I enabled the gps--knowing it would cause the mouse jumpie thing. I managed to get the mouse to sit still for a sec and shut down the machine-- I didn't even log on.
Went back into bios and disabled GPS again
Rebooted, logged in, and now the GPS fix works.
Don't ask me why, but its happy now that I turned GPS on, and back off again. Not sure if it did something in registry that let the merge happen or what--not going to investigate further--but suspect windows sees the GPS and adds something to the registry.
So it was a driver issue that changed the settings.
ASKER
apparently? I would think I would be able to merge a full registry key to the registry whether the driver was installed or not.,
of course a more detailed message from M$ would/could have pointed that direction....
of course a more detailed message from M$ would/could have pointed that direction....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for your help!
Tricky issue this one and I was happy to work with you
The home for the key changed upon Windows Reinstall. That would be one possible reason.