[dbCooker]

I am stuck trying to write in the system32 folder.

For context, it is a dell laptop running windows 10 pro, I do not have administrative permissions.
The only drive available on the machine is labelled as "network" as it runs from a remote server rather than a regular hdd or ssd.


I've booted into repair mode, accessed command prompt. From there I entered notepad and the file explorer.

I went into the system32 directory however it is read only, when I tried to boot into safe mode it asked me for an admin username and password.

I am able to change the bios settings in start-up however resetting the laptop is not an option.


Does anyone know any way to bypass this without running a linux os and trying to mount the drive?

Thanks everyone,

dbCooker

[DramaKing]

I am stuck trying to write in the system32 folder.

For context, it is a dell laptop running windows 10 pro, I do not have administrative permissions.
The only drive available on the machine is labelled as "network" as it runs from a remote server rather than a regular hdd or ssd.

First problem: laptops do not run from remote servers. It's possible that the internal drive has been removed, but this would be highly strange.

---

I've booted into repair mode, accessed command prompt. From there I entered notepad and the file explorer.

I went into the system32 directory however it is read only, when I tried to boot into safe mode it asked me for an admin username and password.

How is this possible when you're running on a remote server?

---

I am able to change the bios settings in start-up however resetting the laptop is not an option.


Does anyone know any way to bypass this without running a linux os and trying to mount the drive?

Thanks everyone,

dbCooker

Neither of these will help with a virtual desktop on a remote server.

Short answer: You can't. There's little legitimate reason to access System32, anyway.

[dbCooker]

Short answer: You can't. There's little legitimate reason to access System32, anyway.

Okay, thanks anyway

[⚡Rednix™]

First problem: laptops do not run from remote servers. It's possible that the internal drive has been removed, but this would be highly strange.

Laptops can run on remote servers easily without any hard drives on a remote network. However the rest of what he said does not make much sense, I agree with you on that part ;)

[DramaKing]

Laptops can run on remote servers easily without any hard drives on a remote network. However the rest of what he said does not make much sense, I agree with you on that part ;)

Have to have some storage for a thin OS with remote desktop. OP doesn't seem willing to explain his hardware setup, even though he isn't a onetime user.

[powisi3138]

I believe you really can't...