I think OP does not want to do the whole sync process from the beginning but I don't think OP has any choice because the re-index will probably restart a new sync process which OP is trying to avoid in the first place ...
Where do you read from OP's post that he tries to avoid a new sync or re-index?
OP clearly states he's not tech-savvy and likely lacks some Bitcoin Core knowledge and thus he doesn't understand what the error message tells him and implications from that.
We can't know for sure why his node is pruned, might just be the default setting and he didn't know about potential consequences, especially when you introduce foreign wallet.dat file to such a pruned node. Could also be that his device lacks the necessary amount of storage to hold an unpruned blockchain.
OP can't avoid a new sync of all blockchain's blocks for his pruned node to properly sync his foreign wallet.dat file.
BitMaxz's solution disables pruned mode only to enable it after deleting blockchain data. OP's node would go back to being a pruned node like it currently is. He won't have to re-download the entire blockchain, ...
To my knowledge turning of pruned mode forces a new IBD when you acknowledge that action when Bitcoin Core tells you about the consequences. Of course you should've the wallet file loaded in Core then. When the new IBD started, you don't have to wait until it finishes, you can re-enable pruned mode if you must due to lack of storage space. Then let Core finish the sync process and your wallet should become fully synced once the full blockchain sync process is finished.
Your device should've better at least 8GB RAM and it helps if you can devote about half of it to dbcache. With 8GB RAM set
dbcache=4096 in your bitcoin.conf file. If you have more RAM and don't need it for other stuff on your device during blockchain sync, assign more of it to dbcache. It speeds up the blockchain sync.