1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

TrustedInstaller

Discussion in 'Windows 7' started by JimBob, Feb 3, 2010.

  1. JimBob

    JimBob Flightless Bird

    Hi,
    Recently installed Win 7 and tried using my floppy drive for first time and
    had some problems with it. After verifying the drive and data cable was
    working OK using my XP box and Win 7 telling me I had the correct drivers
    for the drive and the controller I decided to try the flpydisk.sys file from
    XP to see if that would make a difference. When trying to us the Device
    Manager to update the driver for the drive using the older file from XP
    Device Manger would not allow me to do it telling me I had the latest
    driver. I then decided to try doing it manually. When trying to move the
    flpydisk.sys file, in Win 7, to the desktop I was told I would have to get
    permission from TrustedInstaller. Having no idea who TrustedInstaller was I
    decided to just take ownership of the file, I only have one user and it's
    setup as administrator, which worked to allow me to move the file and try
    the XP file which helped some but didn't fully correct the problems I was
    having. I then put the original file back and attempted to change the
    ownership back to TrustedInstaller. Windows then told me, in so many words,
    TrustedInstaller was an invalid name. I sure would appreciate if anyone can
    clue me in on who the TrustedInstaller is and why Win 7 won't allow me to
    put it back.
    Thanks for any info.
     
  2. Seth

    Seth Flightless Bird

    "JimBob" <user@home.invalid> wrote in message
    news:hkbquk$pej$1@speranza.aioe.org...
    > Hi,
    > Recently installed Win 7 and tried using my floppy drive for first time
    > and had some problems with it. After verifying the drive and data cable
    > was working OK using my XP box and Win 7 telling me I had the correct
    > drivers for the drive and the controller I decided to try the flpydisk.sys
    > file from XP to see if that would make a difference. When trying to us the
    > Device Manager to update the driver for the drive using the older file
    > from XP Device Manger would not allow me to do it telling me I had the
    > latest driver. I then decided to try doing it manually. When trying to
    > move the flpydisk.sys file, in Win 7, to the desktop I was told I would
    > have to get permission from TrustedInstaller. Having no idea who
    > TrustedInstaller was I decided to just take ownership of the file, I only
    > have one user and it's setup as administrator, which worked to allow me to
    > move the file and try the XP file which helped some but didn't fully
    > correct the problems I was having. I then put the original file back and
    > attempted to change the ownership back to TrustedInstaller. Windows then
    > told me, in so many words, TrustedInstaller was an invalid name. I sure
    > would appreciate if anyone can clue me in on who the TrustedInstaller is
    > and why Win 7 won't allow me to put it back.



    "TrsutedInstaller" is more of a process than a conventional user. It's fully
    qualified name is NT SERVICE\TrustedInstaller.

    See here...
    http://www.vistax64.com/tutorials/159360-trustedinstaller-restore-owner.html
     
  3. JimBob

    JimBob Flightless Bird

    "Seth" <seth_lermanNOSPAM@hotmail.com> wrote in message
    news:hkc06l$pnn$1@news.eternal-september.org...
    > "JimBob" <user@home.invalid> wrote in message
    > news:hkbquk$pej$1@speranza.aioe.org...
    >> Hi,
    >> Recently installed Win 7 and tried using my floppy drive for first time
    >> and had some problems with it. After verifying the drive and data cable
    >> was working OK using my XP box and Win 7 telling me I had the correct
    >> drivers for the drive and the controller I decided to try the
    >> flpydisk.sys file from XP to see if that would make a difference. When
    >> trying to us the Device Manager to update the driver for the drive using
    >> the older file from XP Device Manger would not allow me to do it telling
    >> me I had the latest driver. I then decided to try doing it manually. When
    >> trying to move the flpydisk.sys file, in Win 7, to the desktop I was told
    >> I would have to get permission from TrustedInstaller. Having no idea who
    >> TrustedInstaller was I decided to just take ownership of the file, I only
    >> have one user and it's setup as administrator, which worked to allow me
    >> to move the file and try the XP file which helped some but didn't fully
    >> correct the problems I was having. I then put the original file back and
    >> attempted to change the ownership back to TrustedInstaller. Windows then
    >> told me, in so many words, TrustedInstaller was an invalid name. I sure
    >> would appreciate if anyone can clue me in on who the TrustedInstaller is
    >> and why Win 7 won't allow me to put it back.

    >
    >
    > "TrsutedInstaller" is more of a process than a conventional user. It's
    > fully qualified name is NT SERVICE\TrustedInstaller.
    >
    > See here...
    > http://www.vistax64.com/tutorials/159360-trustedinstaller-restore-owner.html
    >


    Hi Seth,
    I really appreciate your response, thank you. I didn't have to try the
    instructions given because I have at least enough sense to use the backup
    program in Win 7 to make a system image. It's good to have that info tucked
    away just in case in the future I happen to have a senior moment and forget
    to make an image when I'm fooling around with the system.
     
  4. Jim

    Jim Flightless Bird

    On Thu, 4 Feb 2010 07:11:02 -0500, "JimBob" <user@home.invalid> wrote:

    >
    >"Seth" <seth_lermanNOSPAM@hotmail.com> wrote in message
    >news:hkc06l$pnn$1@news.eternal-september.org...
    >> "JimBob" <user@home.invalid> wrote in message
    >> news:hkbquk$pej$1@speranza.aioe.org...
    >>> Hi,
    >>> Recently installed Win 7 and tried using my floppy drive for first time
    >>> and had some problems with it. After verifying the drive and data cable
    >>> was working OK using my XP box and Win 7 telling me I had the correct
    >>> drivers for the drive and the controller I decided to try the
    >>> flpydisk.sys file from XP to see if that would make a difference. When
    >>> trying to us the Device Manager to update the driver for the drive using
    >>> the older file from XP Device Manger would not allow me to do it telling
    >>> me I had the latest driver. I then decided to try doing it manually. When
    >>> trying to move the flpydisk.sys file, in Win 7, to the desktop I was told
    >>> I would have to get permission from TrustedInstaller. Having no idea who
    >>> TrustedInstaller was I decided to just take ownership of the file, I only
    >>> have one user and it's setup as administrator, which worked to allow me
    >>> to move the file and try the XP file which helped some but didn't fully
    >>> correct the problems I was having. I then put the original file back and
    >>> attempted to change the ownership back to TrustedInstaller. Windows then
    >>> told me, in so many words, TrustedInstaller was an invalid name. I sure
    >>> would appreciate if anyone can clue me in on who the TrustedInstaller is
    >>> and why Win 7 won't allow me to put it back.

    >>
    >>
    >> "TrsutedInstaller" is more of a process than a conventional user. It's
    >> fully qualified name is NT SERVICE\TrustedInstaller.
    >>
    >> See here...
    >> http://www.vistax64.com/tutorials/159360-trustedinstaller-restore-owner.html
    >>

    >
    >Hi Seth,
    >I really appreciate your response, thank you. I didn't have to try the
    >instructions given because I have at least enough sense to use the backup
    >program in Win 7 to make a system image. It's good to have that info tucked
    >away just in case in the future I happen to have a senior moment and forget
    >to make an image when I'm fooling around with the system.
    >


    Hope the image is on an external hd .
     
  5. JimBob

    JimBob Flightless Bird

    "Jim" <bojimbo261@aol.com> wrote in message
    news:0jbmm5hjq5f32tu6gac1svdc94ijldr3mo@4ax.com...
    > On Thu, 4 Feb 2010 07:11:02 -0500, "JimBob" <user@home.invalid> wrote:
    >
    >>
    >>"Seth" <seth_lermanNOSPAM@hotmail.com> wrote in message
    >>news:hkc06l$pnn$1@news.eternal-september.org...
    >>> "JimBob" <user@home.invalid> wrote in message
    >>> news:hkbquk$pej$1@speranza.aioe.org...
    >>>> Hi,
    >>>> Recently installed Win 7 and tried using my floppy drive for first time
    >>>> and had some problems with it. After verifying the drive and data cable
    >>>> was working OK using my XP box and Win 7 telling me I had the correct
    >>>> drivers for the drive and the controller I decided to try the
    >>>> flpydisk.sys file from XP to see if that would make a difference. When
    >>>> trying to us the Device Manager to update the driver for the drive
    >>>> using
    >>>> the older file from XP Device Manger would not allow me to do it
    >>>> telling
    >>>> me I had the latest driver. I then decided to try doing it manually.
    >>>> When
    >>>> trying to move the flpydisk.sys file, in Win 7, to the desktop I was
    >>>> told
    >>>> I would have to get permission from TrustedInstaller. Having no idea
    >>>> who
    >>>> TrustedInstaller was I decided to just take ownership of the file, I
    >>>> only
    >>>> have one user and it's setup as administrator, which worked to allow me
    >>>> to move the file and try the XP file which helped some but didn't fully
    >>>> correct the problems I was having. I then put the original file back
    >>>> and
    >>>> attempted to change the ownership back to TrustedInstaller. Windows
    >>>> then
    >>>> told me, in so many words, TrustedInstaller was an invalid name. I sure
    >>>> would appreciate if anyone can clue me in on who the TrustedInstaller
    >>>> is
    >>>> and why Win 7 won't allow me to put it back.
    >>>
    >>>
    >>> "TrsutedInstaller" is more of a process than a conventional user. It's
    >>> fully qualified name is NT SERVICE\TrustedInstaller.
    >>>
    >>> See here...
    >>> http://www.vistax64.com/tutorials/159360-trustedinstaller-restore-owner.html
    >>>

    >>
    >>Hi Seth,
    >>I really appreciate your response, thank you. I didn't have to try the
    >>instructions given because I have at least enough sense to use the backup
    >>program in Win 7 to make a system image. It's good to have that info
    >>tucked
    >>away just in case in the future I happen to have a senior moment and
    >>forget
    >>to make an image when I'm fooling around with the system.
    >>

    >
    > Hope the image is on an external hd .


    Hi Jim,
    I do not have an external HD. The image is on drive D my second internal HD
    and I have a repair disk for Win 7 shouldn't that be adequate.
     
  6. Gene E. Bloch

    Gene E. Bloch Flightless Bird

    On 2/05/10, JimBob posted:
    > "Jim" <bojimbo261@aol.com> wrote in message
    > news:0jbmm5hjq5f32tu6gac1svdc94ijldr3mo@4ax.com...
    >> On Thu, 4 Feb 2010 07:11:02 -0500, "JimBob" <user@home.invalid> wrote:
    >>
    >>>
    >>>"Seth" <seth_lermanNOSPAM@hotmail.com> wrote in message
    >>>news:hkc06l$pnn$1@news.eternal-september.org...
    >>>> "JimBob" <user@home.invalid> wrote in message
    >>>> news:hkbquk$pej$1@speranza.aioe.org...
    >>>>> Hi,
    >>>>> Recently installed Win 7 and tried using my floppy drive for first time
    >>>>> and had some problems with it. After verifying the drive and data cable
    >>>>> was working OK using my XP box and Win 7 telling me I had the correct
    >>>>> drivers for the drive and the controller I decided to try the
    >>>>> flpydisk.sys file from XP to see if that would make a difference. When
    >>>>> trying to us the Device Manager to update the driver for the drive using
    >>>>> the older file from XP Device Manger would not allow me to do it telling
    >>>>> me I had the latest driver. I then decided to try doing it manually.
    >>>>> When
    >>>>> trying to move the flpydisk.sys file, in Win 7, to the desktop I was
    >>>>> told
    >>>>> I would have to get permission from TrustedInstaller. Having no idea who
    >>>>> TrustedInstaller was I decided to just take ownership of the file, I
    >>>>> only
    >>>>> have one user and it's setup as administrator, which worked to allow me
    >>>>> to move the file and try the XP file which helped some but didn't fully
    >>>>> correct the problems I was having. I then put the original file back and
    >>>>> attempted to change the ownership back to TrustedInstaller. Windows then
    >>>>> told me, in so many words, TrustedInstaller was an invalid name. I sure
    >>>>> would appreciate if anyone can clue me in on who the TrustedInstaller is
    >>>>> and why Win 7 won't allow me to put it back.
    >>>>
    >>>>
    >>>> "TrsutedInstaller" is more of a process than a conventional user. It's
    >>>> fully qualified name is NT SERVICE\TrustedInstaller.
    >>>>
    >>>> See here...
    >>>> http://www.vistax64.com/tutorials/159360-trustedinstaller-restore-owner.html
    >>>>
    >>>
    >>>Hi Seth,
    >>>I really appreciate your response, thank you. I didn't have to try the
    >>>instructions given because I have at least enough sense to use the backup
    >>>program in Win 7 to make a system image. It's good to have that info tucked
    >>>away just in case in the future I happen to have a senior moment and forget
    >>>to make an image when I'm fooling around with the system.
    >>>

    >>
    >> Hope the image is on an external hd .


    > Hi Jim,
    > I do not have an external HD. The image is on drive D my second internal HD
    > and I have a repair disk for Win 7 shouldn't that be adequate.


    If it's indeed a second drive and not a partition on the first, that's
    sort of OK, IMO. If your computer has an electrical glitch that kills
    the D: drive as well as the C: drive, or is stolen, however, you've
    lost all...

    An external drive is slower, but safer from the electrical problem. It
    could also end up not being stolen if it was nowhere near the computer.

    I prefer an external drive, as you can see, but the scenarios I
    describe might seem like a bit of a stretch :)

    --
    Gene Bloch 650.366.4267 lettersatblochg.com
     
  7. JimBob

    JimBob Flightless Bird

    "Gene E. Bloch" <letters@someplace.invalid> wrote in message
    news:hki1re$eoh$1@news.albasani.net...
    > On 2/05/10, JimBob posted:
    >> "Jim" <bojimbo261@aol.com> wrote in message
    >> news:0jbmm5hjq5f32tu6gac1svdc94ijldr3mo@4ax.com...
    >>> On Thu, 4 Feb 2010 07:11:02 -0500, "JimBob" <user@home.invalid> wrote:

    >
    > If it's indeed a second drive and not a partition on the first, that's
    > sort of OK, IMO. If your computer has an electrical glitch that kills the
    > D: drive as well as the C: drive, or is stolen, however, you've lost
    > all...
    >
    > An external drive is slower, but safer from the electrical problem. It
    > could also end up not being stolen if it was nowhere near the computer.
    >
    > I prefer an external drive, as you can see, but the scenarios I describe
    > might seem like a bit of a stretch :)
    >
    > --
    > Gene Bloch 650.366.4267 lettersatblochg.com
    >
    >


    Hi Gene,
    Your input is appreciated. Thank you.
     

Share This Page